Date: Fri, 14 Nov 1997 17:54:31 -0800 (PST) From: asami@cs.berkeley.edu (Satoshi Asami) To: max@wide.ad.jp Cc: gj@freebsd.org, cvs-committers@freebsd.org, cvs-all@freebsd.org, cvs-ports@freebsd.org, max@wide.ad.jp Subject: Re: /var/run/<dir> Message-ID: <199711150154.RAA01250@bubble.didi.com> In-Reply-To: <199711140744.QAA10961@access.sfc.wide.ad.jp> (message from Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= on Fri, 14 Nov 1997 16:44:23 %2B0900)
next in thread | previous in thread | raw e-mail | index | archive | help
* 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. I don't think we need to change /etc/rc for this. Let the startup scripts ensure whatever they want. In most cases, a simple "mkdir -p; chown" should suffice. * 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.) Too dangerous for some cases. * 3. Change the permission of the /var/run directory to bin.bin 1777. Not my area. ;) * 4. In /etc/rc, do rm -rf and create /var/run/user (or whatever) with * the permission of 1777. That sounds ok for pid files, but for lock files, doesn't emacs need a directory to already exist? Or will it create it if necessary? * 5. The directory /var/run isn't proper place for this purpose in the * first place. The only other places that can be used are: /tmp (the whole thing could be gone by reboot) /var/tmp (will survive reboots) /var/db (lock files don't really belong here) They all don't seem right. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711150154.RAA01250>