Date: Wed, 7 Oct 1998 17:34:41 -0700 (PDT) From: asami@FreeBSD.org (Satoshi Asami) To: skynyrd@opus.cts.cwu.edu Cc: nate@mt.sri.com, cvs-committers@FreeBSD.org Subject: Re: cvs commit: ports/editors/xemacs Makefile ports/editors/xemacs/files xemacs.sh Message-ID: <199810080034.RAA11770@silvia.hip.berkeley.edu> In-Reply-To: <Pine.BSF.3.96.981007170445.897K-100000@opus.cts.cwu.edu> (message from Chris Timmons on Wed, 7 Oct 1998 17:06:22 -0700 (PDT))
next in thread | previous in thread | raw e-mail | index | archive | help
* Why not use /var/spool/lock to contain the directory? I think it would be
I have no idea why "lock" ended up in there in the first place. The
only reason I can think of is because it is used by uucp, which is a
large consumer of the /var/spool hierarchy.
* kind of goofy to have a {PREFIX}/etc/rc.d script create xemacs' lock file
* directory each time the machine boots up!
The script still needs to be somewhere to delete bogus lock files
after a crash.
Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810080034.RAA11770>