Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Nov 2002 10:58:37 -0800
From:      "Drew Tomlinson" <drew@mykitchentable.net>
To:        "Matthew Emmerton" <matt@gsicomp.on.ca>, "FreeBSD Questions" <freebsd-questions@FreeBSD.ORG>
Subject:   Re: vi Error - Permission Denied
Message-ID:  <03d501c28b46$acc66550$6e2a6ba5@tagalong>
References:  <03c701c28b42$94efc880$6e2a6ba5@tagalong> <008701c28b44$2c596bd0$1200a8c0@gsicomp.on.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Matthew Emmerton" <matt@gsicomp.on.ca>
Sent: Wednesday, November 13, 2002 10:40 AM


> > I've decided to try and wean myself off ee and move to vi.  I have
two
> > boxes, both running 4.7-RELEASE-p1.  On one, I tried the following
> > logged on with normal user privileges:
> >
> > blacklamb> vi practice
> > ex/vi: Error: Unable to create temporary file: Permission denied
> >
> > A google search on this error suggests that permissions are not set
> > correctly on /var/tmp and /var/tmp/vi.recover so I check them and
they
> > appear to be OK.
> >
> > blacklamb# ls -ld /var/tmp
> > drwxrwxrwt  3 root  wheel  512 Nov 13 08:45 /var/tmp
> >
> > blacklamb# ls -ld /var/tmp/vi.recover
> > drwxrwxrwt  2 root  wheel  512 Nov 10 12:22 /var/tmp/vi.recover
> >
> > So I check my other system and the permissions are the same, yet I
can
> > use vi logged on with normal privledges.  Any ideas on what is wrong
> > here?
>
> Usually what this means is that the temporary filename that vi has
generated
> and is attempting to use is _the same_ as an existing temporary file
in
> /var/tmp.

Thanks for your response, however I don't think this is my problem.  My
/var directory doesn't contain any files, just directories:

blacklamb# ll /var
drwxr-xr-x   2 root    wheel    512 Jun 12  2001 account
drwxr-xr-x   4 root    wheel    512 Jun 12  2001 at
drwxr-x---   2 root    wheel    512 Oct  9 03:01 backups
drwxr-x---   2 root    wheel    512 Jun 13  2001 crash
drwxr-x---   3 root    wheel    512 Jul  6 12:10 cron
drwxr-xr-x   6 root    wheel    512 Jun 15 08:56 db
dr-xr-xr-x   2 root    wheel    512 Nov  8 06:07 empty
drwxrwxr-x   5 root    games    512 Jun 13  2001 games
drwx------   2 root    wheel    512 Sep 20  2001 heimdal
drwxr-xr-x   3 root    wheel    512 Jun 13 09:53 lib
drwxr-xr-x   3 root    wheel    512 Dec  5  2001 local
drwxr-xr-x   2 root    wheel    512 Nov 13 10:45 lock
drwxr-xr-x   5 root    wheel   7168 Nov 13 00:00 log
drwxrwxr-x   2 root    mail     512 Oct  8 10:07 mail
drwxr-xr-x   2 daemon  wheel    512 Jun 13  2001 msgs
drwxr-xr-x   2 root    wheel    512 Nov 12 15:29 net-snmp
drwxr-xr-x   2 root    wheel    512 Jun 12  2001 preserve
drwxr-xr-x   3 root    wheel   1024 Nov 13 09:00 run
drwxrwxr-x   2 root    daemon   512 Jun 12  2001 rwho
drwxr-xr-x  13 root    wheel    512 Nov 13 08:45 spool
drwxrwxrwt   3 root    wheel    512 Nov 13 08:45 tmp
drwxr-xr-x   2 root    wheel    512 Nov  8 20:51 yp

/var/tmp only contains the vi.recover directory and /var/tmp/vi.recover
is empty.


> I don't usually see this on my small FreeBSD machines at home, but I
do see
> this quite frequently on the large multi-user (200+) AIX machines that
I use
> at work where it's not uncommon for people to have 4 or 5 instances of
vi
> running at once.

Both of my servers are small home machines.  I am the only user.  Any
other ideas?

Thanks,

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03d501c28b46$acc66550$6e2a6ba5>