From owner-cvs-all Wed Oct 7 17:25:11 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03256 for cvs-all-outgoing; Wed, 7 Oct 1998 17:25:11 -0700 (PDT) (envelope-from owner-cvs-all) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03243 for ; Wed, 7 Oct 1998 17:25:07 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id RAA06077; Wed, 7 Oct 1998 17:06:22 -0700 (PDT) Date: Wed, 7 Oct 1998 17:06:22 -0700 (PDT) From: Chris Timmons To: Nate Williams cc: cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: ports/editors/xemacs Makefile ports/editors/xemacs/files xemacs.sh In-Reply-To: <199810072310.RAA17369@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Why not use /var/spool/lock to contain the directory? I think it would be kind of goofy to have a {PREFIX}/etc/rc.d script create xemacs' lock file directory each time the machine boots up! -Chris On Wed, 7 Oct 1998, Nate Williams wrote: > > Modified files: > > editors/xemacs Makefile > > editors/xemacs/files xemacs.sh > > Log: > > Change the lock directory to /var/run/emacs/lock per Satoshi's > > request. > > Note, this gets wiped at boot-time with the new /etc files, so > *something* better be recreating it else xemacs won't have a lock > directory. > > (This bit me earlier today...) > > > > Nate