Date: Fri, 14 Nov 1997 16:44:23 +0900 From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp> To: gj@FreeBSD.ORG Cc: max@wide.ad.jp Subject: /var/run/<dir> Message-ID: <199711140744.QAA10961@access.sfc.wide.ad.jp> In-Reply-To: Your message of "Sat, 8 Nov 1997 14:19:03 -0800 (PST)" References: <199711082219.OAA22638@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
gj> gj 1997/11/08 14:19:03 PST
gj> Modified files:
gj> editors/xemacs20 Makefile
gj> Log:
gj> Put the lock file in /var/run/xemacs/lock rather than
gj> ${PREFIX}/lib/xemacs/lock.
gj> Also modify post-install to set the permissions on /var/run/xemacs/lock,
gj> ${PREFIX}/lib/xemacs/site-lisp and ${PREFIX}/share/xemacs/site-lisp, as
gj> done in PLIST, since ``make install'' doesn't do it.
Here it is. Another port that needs a directory in /var/run.
If I'm not missing anything, these are the ideas that were posted in
response to the discussion I called:
1. Modify /etc/rc to do rm -rf /var/run/* and let the startup scripts
of each program (rc.d/*.sh) make necessary directory with appropriate
permission and let the program make necessary pid/lock files in the
directory.
2. Open necessary files in /var/run with appropriate permission as
root and then run the program. (This assumes that the program won't
unlink existing pid/lock/whatever files before creating new one.)
3. Change the permission of the /var/run directory to bin.bin 1777.
4. In /etc/rc, do rm -rf and create /var/run/user (or whatever) with
the permission of 1777.
5. The directory /var/run isn't proper place for this purpose in the
first place.
What do people think? Which one seems the best? Any other idea?
Cheers,
Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711140744.QAA10961>