Date: Sat, 8 Nov 2003 17:39:19 -0500 (EST) From: Eric van Gyzen <vangyzen@stat.duke.edu> To: FreeBSD-gnats-submit@FreeBSD.org Subject: conf/59065: /tmp/.X0-lock is not removed if clear_tmp_enable is not enabled Message-ID: <20031108223919.51980FD040@amelia.vangyzen.net> Resent-Message-ID: <200311082350.hA8NoGdX092503@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 59065 >Category: conf >Synopsis: /tmp/.X0-lock is not removed if clear_tmp_enable is not enabled >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Nov 08 15:50:15 PST 2003 >Closed-Date: >Last-Modified: >Originator: Eric van Gyzen >Release: FreeBSD 5.1-RELEASE-p10 i386 >Organization: Duke University Statistics >Environment: FreeBSD 5.1-RELEASE-p10 i386 >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. >How-To-Repeat: N/A >Fix: Perhaps someone more familiar with the rc system could suggest a fix... >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031108223919.51980FD040>