Path: utzoo!mnetor!uunet!mcvax!cernvax!hslrswi!pan!jw
From: jw@pan.UUCP (Jamie Watson)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: Dial in/out on one line?
Message-ID: <385@pan.UUCP>
Date: 24 Mar 88 06:30:46 GMT
References: <381@pan.UUCP> <5424@spool.cs.wisc.edu>
Reply-To: jw@pan.UUCP (Jamie Watson)
Organization: Pansystem Informatics AG, Zuerich, Switzerland
Lines: 24

In article <5424@spool.cs.wisc.edu> luner@ai.cs.wisc.edu (David L. Luner) writes:
>I believe that this is a "restriction." A port cannot be set up for both
>dial-in and dial-out UUCP access. The way around this is to have a cron or
>at job pdisable the port prior to when uucp is going to try to call out.
>I hope to have a better solution in the future, but I wouldn't hold my
>breath.

But you see, "pdisable/penable" is not the problem!  The uucico program does
that (at least, when run with -x9 it claims to do that), but then it can't
open the serial line, because the line is owned by root and mode 622.  I can
either the owner or mode by hand, and then everything works.  But the next
time a new getty is spawned, the owner and modes are changed back, and I'm
stuck again.

So far the best I can think of is to limit callout times, and have a cron
script which sets the owner and mode a the beginning of that time.  This is
not only ugly, though, it is prone to failure.

The fact that uucico diables and enables the port makes me believe that
someone intended for dialin/dialout on one line to work.  I'm hoping that
I just need to make some special kind of L-devices file entry, or something,
but perhaps they just never quite got it done right.

jw