From owner-freebsd-ports  Fri Nov 14 00:27:58 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id AAA11035
          for ports-outgoing; Fri, 14 Nov 1997 00:27:58 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA11029
          for <freebsd-ports@freebsd.org>; Fri, 14 Nov 1997 00:27:51 -0800 (PST)
          (envelope-from sheldonh@axl.iafrica.com)
Received: from axl.iafrica.com [196.31.1.167] (sheldonh)
	by lists01.iafrica.com with esmtp (Exim 1.73 #1)
	id 0xWH3p-0007QL-00; Fri, 14 Nov 1997 10:25:05 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: Masafumi NAKANE <max@wide.ad.jp>
cc: freebsd-ports@freebsd.org
Subject: Re: /var/run/<dir> 
In-reply-to: Your message of "Fri, 14 Nov 1997 16:44:23 +0900."
             <199711140744.QAA10961@access.sfc.wide.ad.jp> 
Date: Fri, 14 Nov 1997 10:25:08 +0200
Message-ID: <24021.879495908@axl.iafrica.com>
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Fri, 14 Nov 1997 16:44:23 +0900, Masafumi NAKAN wrote:

> 5. The directory /var/run isn't proper place for this purpose in the
> first place.

I suppose /tmp is still out of the question since the last time I
mentioned it? Is this being decided by hier(7) or by undocumented
religious concerns?

hier(7):
     /tmp/   temporary files, usually a mfs(8) memory-based filesystem
              (the contents of /tmp are usually NOT preserved across a
              system re- boot)

Regardless, it's evident that xemacs would benefit from an
rc.d/xemacs.sh that puts its lockdir somewhere?

Of course, the real solution is probably to hack up xemacs' naming
system for its lock files so they can go wherever without running the
risk of bumping into someone _else's_ lock files.

2c.sheldonh