From owner-freebsd-current Mon Jul 3 08:52:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA10471 for current-outgoing; Mon, 3 Jul 1995 08:52:02 -0700 Received: from wc.cdrom.com (wc.cdrom.com [192.216.223.37]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA10465 for ; Mon, 3 Jul 1995 08:52:01 -0700 Received: from id.slip.bcm.tmc.edu (root@[128.249.248.67]) by wc.cdrom.com (8.6.12/8.6.12) with ESMTP id IAA29632 for ; Mon, 3 Jul 1995 08:51:55 -0700 Received: (from rich@localhost) by id.slip.bcm.tmc.edu (8.6.11/8.6.9) id KAA02622; Mon, 3 Jul 1995 10:50:40 -0500 Date: Mon, 3 Jul 1995 10:50:40 -0500 From: Rich Murphey Message-Id: <199507031550.KAA02622@id.slip.bcm.tmc.edu> To: freebsd-current@freebsd.org In-reply-to: <199507030908.LAA03564@uriah.heep.sax.de> (message from J Wunsch on Mon, 3 Jul 1995 11:08:53 +0200 (MET DST)) Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" Reply-to: rich@lamprey.utmb.edu Sender: current-owner@freebsd.org Precedence: bulk |From: J Wunsch |Basically means that iijppp is broken in this respect. Clients are |encouraged to examine an existing lock file to see if it's a stale |lock (by trying to send a signal to the process). It's safe for them |to remove the lock file if the process holding the lock disappeared. | |Lock files suck. They should not be used at all, and the only client |that really needs them right now is mgetty. What if you wanted to run outgoing hylafax and outgoing 'ppp -auto' on the same port.