From owner-cvs-ports  Thu Nov 13 23:44:56 1997
Return-Path: <owner-cvs-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA08260
          for cvs-ports-outgoing; Thu, 13 Nov 1997 23:44:56 -0800 (PST)
          (envelope-from owner-cvs-ports)
Received: from access.sfc.wide.ad.jp (bourbon.sfc.wide.ad.jp [203.178.141.171])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA08237;
          Thu, 13 Nov 1997 23:44:33 -0800 (PST)
          (envelope-from max@bourbon.sfc.wide.ad.jp)
Received: from bourbon.sfc.wide.ad.jp (localhost [127.0.0.1]) by access.sfc.wide.ad.jp (8.8.7/3.5Wpl107/15/97) with ESMTP id QAA10961; Fri, 14 Nov 1997 16:44:24 +0900 (JST)
Message-Id: <199711140744.QAA10961@access.sfc.wide.ad.jp>
To: gj@FreeBSD.ORG
Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG
Cc: max@wide.ad.jp
Subject: /var/run/<dir>
From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp>
In-Reply-To: Your message of "Sat, 8 Nov 1997 14:19:03 -0800 (PST)"
References: <199711082219.OAA22638@freefall.freebsd.org>
X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3
X-PGP-Fingerprint: 00 D8 2C CA C7 75 D4 40  5C 34 39 BA A5 46 C0 CC
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Nov 1997 16:44:23 +0900
Sender: owner-cvs-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

    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