From owner-freebsd-current Thu Jul 6 17:22:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA10066 for current-outgoing; Thu, 6 Jul 1995 17:22:53 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id RAA10060 for ; Thu, 6 Jul 1995 17:22:50 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA08197; Fri, 7 Jul 1995 02:22:48 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA13121 for freebsd-current@freebsd.org; Fri, 7 Jul 1995 02:22:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id PAA10254 for freebsd-current@freebsd.org; Thu, 6 Jul 1995 15:21:02 +0200 From: J Wunsch Message-Id: <199507061321.PAA10254@uriah.heep.sax.de> Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" To: freebsd-current@freebsd.org Date: Thu, 6 Jul 1995 15:21:02 +0200 (MET DST) Reply-To: freebsd-current@freebsd.org In-Reply-To: <199507051257.OAA01902@vector.eikon.e-technik.tu-muenchen.de> from "Julian Stacey" at Jul 5, 95 02:57:31 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 995 Sender: current-owner@freebsd.org Precedence: bulk As Julian Stacey wrote: > > > > From: J Wunsch > > Lock files suck. They should not be used at all, and the only client > > that really needs them right now is mgetty. > > My /var/spool/fax/etc/config.ttyd1 (for hylafax) has: > UUCPLockDir /var/spool/lock # jhs added this after seeing where kermit created a lock. > I haven't got round to checking if I need it. If it's outgoing-only, it isn't needed. If it's also able to receive incoming fax messages, i guess you're going to use mgetty anyway. mgetty needs the lock files, since it cannot use the dialin port (it has to watch modem messages even while the modem is in the `not connected' state). The only way around would be to unblock the open() on a dialin port already on the `ring indicator' line instead of the `data carrier detect', as Terry once proposed. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)