Date: Sat, 13 May 2000 05:20:02 -0700 (PDT) From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/18461: vi.recover misplaced in /var/tmp Message-ID: <200005131220.FAA59129@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/18461; it has been noted by GNATS.
From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
To: Gregory Bond <gnb@itga.com.au>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: conf/18461: vi.recover misplaced in /var/tmp
Date: Sat, 13 May 2000 14:07:23 +0200
-On [20000509 12:01], Gregory Bond (gnb@itga.com.au) wrote:
>
>From: Gregory Bond <gnb@itga.com.au>
>
> > vi.recover should not be in /var/tmp. imagine the case
> > where /var/tmp is a memory filesystem. upon reboot,
> > everything is lost.
>
> On the contrary, /var/tmp is exactly the right spot for vi.recover, because
> /var/tmp is -explicitly documented- to remain over reboots. See "man hier".
>
> Anyone who uses mfs for /var/tmp is just plain wrong.
I agree with the above sentiment, from hier(7):
/tmp/ temporary files, usually a mfs(8) memory-based filesystem (the
contents of /tmp are usually NOT preserved across a system re-
boot)
/var/ multi-purpose log, temporary, transient, and spool files
tmp/ temporary files that are kept between system reboots
vi.recover/
the directory where recovery files are
stored
This is also why there is a clear_tmp_enable directive in the rc.conf.
--
Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/C-rated Coder BSD: Technical excellence at its best
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>;
And every word upon your spiralling cross is but a misled sun, a bitter
loss...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005131220.FAA59129>