From owner-freebsd-ports Thu Nov 20 15:03:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16753 for ports-outgoing; Thu, 20 Nov 1997 15:03:48 -0800 (PST) (envelope-from owner-freebsd-ports) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16731; Thu, 20 Nov 1997 15:03:36 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.7/8.8.7) with SMTP id PAA17092; Thu, 20 Nov 1997 15:03:07 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Thu, 20 Nov 1997 15:03:07 -0800 (PST) From: Chris Timmons To: Satoshi Asami cc: mark@grondar.za, chuckr@glue.umd.edu, axl@iafrica.com, gj@freebsd.org, freebsd-ports@freebsd.org Subject: Politics of /var/run (was xemacs world writable dir) In-Reply-To: <199711080248.SAA02354@vader.cs> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't have a better idea, but our /var/run/xemacs directory makes bootup a little bit more verbose when line #98 of /etc/rc comes along. Should anything that goes into /var/run be removable in this fashion, including directories? 1 #!/bin/sh 2 # $Id: rc,v 1.104.2.24 1997/09/21 16:10:34 joerg Exp $ 3 # From: @(#)rc 5.27 (Berkeley) 6/5/91 95 96 adjkerntz -i 97 98 rm -f /var/run/* 99 100 # Keep a copy of the boot messages around 101 dmesg > /var/run/dmesg.boot -Chris On Fri, 7 Nov 1997, Satoshi Asami wrote: > * Souldn't it be at least mode 1777? There is also the possibility of > * putting locks into (eg) /var/tmp, var/spool/lock and so on. > > These files don't need to live past reboots (right?) so I guess they > go in /var/run. (What was the result of the discussion about the > permission on that dir, Max?) > > I see that mule has a lock dir, but emacs doesn't. do you what's > going on? > > Satoshi >