From owner-freebsd-current Mon Jul 3 10:33:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA15645 for current-outgoing; Mon, 3 Jul 1995 10:33:48 -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 KAA15637 for ; Mon, 3 Jul 1995 10:33:47 -0700 Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by wc.cdrom.com (8.6.12/8.6.12) with ESMTP id KAA00670 for ; Mon, 3 Jul 1995 10:33:41 -0700 Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.6.11/8.6.9) with SMTP id NAA00300; Mon, 3 Jul 1995 13:30:12 -0400 Received: from localhost by mumps.pfcs.com with SMTP id AA28476 (5.67b/IDA-1.5); Mon, 3 Jul 1995 13:30:28 -0400 To: freebsd-current@FreeBSD.org (FreeBSD-current users), joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: Harlan.Stenn@pfcs.com (Harlan Stenn) Subject: Re: /etc/rc and "rm -f /var/spool/lock/*" In-Reply-To: J Wunsch's (j@uriah.heep.sax.de) message dated Mon, 03 Jul 1995 11:08:53. <199507030908.LAA03564@uriah.heep.sax.de> Date: Mon, 03 Jul 1995 13:30:28 -0300 Message-Id: <28474.804792628@mumps.pfcs.com> From: Harlan Stenn Sender: current-owner@FreeBSD.org Precedence: bulk I suspect the real solution, then, will be to file ijppp. The problem is that when I start up "ppp -auto", it will almost always come up with the same PID as the one from the previous boot, so if the lock file stuck around it will mostlikely have the *same* PID in there, and will then quietly loop until the lock file goes away! This problem happens to me a lot because ijppp frequently terminates, and if I restart ppp the machine will reboot the instant "something" happens on the link. Perhaps it's a nameserver call, perhaps it's simply an IP packet that wants to be handled by the PPP link - I can't tell; no panic is generated so I don't get a core file. H