Date: Sun, 9 Nov 2003 14:50:16 -0800 (PST) From: Kris Kennaway <kris@obsecurity.org> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/59065: /tmp/.X0-lock is not removed if clear_tmp_enable is not enabled Message-ID: <200311092250.hA9MoGLe029341@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/59065; it has been noted by GNATS. From: Kris Kennaway <kris@obsecurity.org> To: Eric van Gyzen <vangyzen@stat.duke.edu> Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: conf/59065: /tmp/.X0-lock is not removed if clear_tmp_enable is not enabled Date: Sun, 9 Nov 2003 14:39:55 -0800 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Nov 08, 2003 at 05:39:19PM -0500, Eric van Gyzen wrote: > >Description: > The /tmp/.X0-lock file is removed by /etc/rc.d/cleartmp, which runs only > if the clear_tmp_enable variable is true. The file should be removed on > boot, unconditionally. I think you got precisely the behaviour you asked for. Many applications use /tmp for storage of lock files and other temporary data - if you want them to restart correctly after a reboot, clear /tmp. Kris --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/rsI7Wry0BWjoQKURAn0xAKDxG8lZ0UmDASw2Uz9VqTb7zjqsygCfcL1C 0jw3b0mofLZ87yiz7YuvUwA= =fNFc -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311092250.hA9MoGLe029341>