Date: Sun, 12 Mar 1995 12:14:48 -0800 From: David Greenman <davidg@Root.COM> To: Joerg Wunsch <joerg@freefall.cdrom.com> Cc: CVS-commiters@freefall.cdrom.com, cvs-sbin@freefall.cdrom.com Subject: Re: cvs commit: src/sbin/slattach slattach.8 slattach.c Message-ID: <199503122014.MAA27866@corbin.Root.COM> In-Reply-To: Your message of "Sun, 12 Mar 95 16:04:22 %2B0100." <199503121504.QAA17660@freefall.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>joerg 95/03/12 16:04:20 > > Modified: sbin/slattach slattach.8 slattach.c > Log: > Make slattach create a PID file under /var/run when the connection is > established. This way, automatic scripts are possible that might > control the SLIP connection. It's unacceptable for a daemon that's > being controlled by a variety of signals to not leave its PID > somewhere. The file name contains the terminal path name component of > the associated tty device, so it should be unique even with multiple > parallel slattach's running. The file will be unlinked at regular exit. I'm not sure this is going to work in all cases that slattach is used. I know of people that start slattach's from floppy (don't we do that on our own install floppies?), and 1) the filesystem is readonly, and 2) /var/run doesn't exist. Do you continue without complaint if the PID file can't be created? Do you continue without complaint if it can't be removed? ...and another thing, what do you do with the PID file when slattach forks (after the HUP on the tty, before the dialer is called)? I would prefer that an option be added to control the creation of the PID file that defaults to *off*. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503122014.MAA27866>