🚀 go-pugleaf

In article <1990Feb7.165016.1304@terminator.cc.umich.edu> mike@shogun.us.cc.umich.edu () writes:
>I have an A/UX system with a single modem attached.  I'd like to use
>this modem for incoming login and outgoing uucp.  The book, Managing
>UUCP and Usenet, gives two suggestions.  One, you can set up multiple
>run levels, like 2 for incoming and 3 for outgoing.  Then you establish
>a schedule and have cron automatically change run levels for you.  This
>works okay but it also seems to start extra crons and lpscheds on me.

We have used this with absolutely no problems.  We also have a "call"
program which allows a user to call out with "cu" if the modem is not
in use.  There is a good deal of cross-checking involved to keep track
of run levels, whether the modem is in use, etc, but it was not very
difficult to get going.  BTW, this is on SysV.  I don't think BSD is
the same and I know SYSIII wasn't.  I have no idea what flavor A/UX is.

>It also says that with BNU (what's BNU?) there's a program called "uugetty"
>which allows the port to be bi-directional without shutting off the uugetty.
>
>Well, this sounds great.  Is there a public domain version of this?  I

There was a program posted a few months ago.  Unfortunately, I forget
the name.  We tried it and it would have worked fine except for the last
step.  Getty normally drops the line when it fires up.  SysV has a
flag that prevents this.  It is not supported on all machines; eg, mine.
This program spawns a getty with the flag as the last step.  On our
machine, it promptly drops the line!


-- 
Bob Peirce, Pittsburgh, PA				  412-471-5320
...!uunet!pitt!investor!rbp			rbp@investor.pgh.pa.us