Date: Tue, 7 Oct 1997 09:18:22 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: bugs@FreeBSD.ORG (FreeBSD Bugs) Cc: Michael@NetworX.ie Subject: Re: sprintf() and UUCP locking Message-ID: <19971007091822.SB13028@uriah.heep.sax.de> In-Reply-To: <ECS9710062258A@NetworX.ie>; from Michael Ryan on Oct 6, 1997 22:52:58 %2B0000 References: <ECS9710062258A@NetworX.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
As Michael Ryan wrote: > Probably nothing major here, but I came across three problems with > slattach in the FreeBSD 2.2.2 release: > > (1) It links in /usr/src/sbin/startslip/uucplock.c for UUCP-style > locking, instead of using /usr/lib/libutil. This has been fixed after 2.2.2 went out the door. > (3) When slattach runs (with the -L flag, the -z flag and -r flag), > mgetty goes apeshite. What's wrong is that, eventhough > slattach uses UUCP locks (which mgetty depends on), it fails to > use them 'properly' as follows: Well, don't use mgetty then. :) Things like this (mgetty's notorious behaviour of wanting to `init' the modem) made me totally mad about it. I'm happy i don't have to use it anymore, and could resort to a plain getty long ago. > The problem lies in steps (d) - (f), namely the lock has been > removed for the duration that the external redial program is > executing. This might be required for some dial programs to work, but i'm not an expert on this. (I don't use startslip, but a homegrewn Perl script instead.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971007091822.SB13028>