From: vince@victrola.wa.com (Vince Skahan) Subject: Re: UUCP on SLS 1.03 Date: 7 Sep 1993 18:03:17 -0700
wlim@gdstech.GRUMMAN.COM (Willie Lim) writes:
>[I think this is a Linux rather than a UUCP question. :-)]
part of it is...
>I have been "playing" the UUCP capability of LInux SLS 1.03 for the
>past few days (and nights. :-)) I used /dev/modem which is softlinked
>to /dev/cua1 (COM 2) with uugetty -r set for /dev/modem in
>/etc/inittab. Also I used Any in the relevent entries in the
>/usr/lib/uucp/Systems file (just to test things out).
>Here are several observations:
>1) When SLS 1.03 is first installed, the system talks to the modem
> (but no dialing out) frequently and then after a while (like an hour
> or more), it leaves the modem alone.
That's not the case with SLS1.02 and uucp didn't change in SLS 1.03.
I'd suggest you turn uugetty off in inittab until you get outgoing calling
working, then add uugetty back. If it breaks then, you have a uugetty
problem.
>2) Having done the necessary modifications to Devices, Dialers, and
> Systems in the /usr/lib/uucp directory and the paths and config
> files in the smail directory (don't remember the exact path
> anymore), I could test my UUCP link using the command:
> /usr/lib/uucico [-f] -x2 -s<hostname>
> Without the -x2 (or higher e.g. x3, x4) flag, Linux would not
> initiate a call otherwise uucico dials out with and without the -f
> or the -r flags set.
Used to be that you needed -x4 for it to work but I think that's fixed
now. I'm not certain what the minimum is with Taylor1.04 or if there
is one at all.
>3) I use crontab to schedule dialouts with the -f and -x2 flag on (I
> want to make sure that the system dials out). Everything works
> fine for a day or so and then
> /usr/lib/uucico -f -r1 -x2 -s<hostname>
> would do nothing except create the LCK..* and TMP...... files
> in /usr/spool/uucp. The audit.local and other logs in the
> /usr/spool/uucp don't seem to get updated when this happens (i.e.,
> when uucico doesn't initiate a dialout). Usually the logs will say
> something or explain why the dialout didn't occur and a couple of
> modem lights will flicker for a few seconds but in this case nothing.
Well if you don't show us the logs, we can't figure it out........
>Questions:
>a) How tightly "hardcoded" is the uucp neighbor "quick" to SLS 1.03?
it isn't. Unless it's your real UUCP neighbor, it shouldn't be in there
at all. Sigh...I can't understand how people keep making the mistake of
taking an example site-specific file and thinking it's valid for all sites
everywhere...
>b) How fast does the C.* and D.* files get created in the
> /usr/spool/uucp/hostname directory? I notice that sometimes those
> files (email addressed to hostname) get created as soon as I "send"
> them out of the mail program (Emacs rmail mode) but then there are times
> I notice that the files don't get created that quickly.
takes a few seconds with sendmail or smail, I dunno with emacs.
>c) I haven't left my system alone long enough (e.g. for > 24 hours)
> to see if the UUCP link will "wake" up again. Is the uucico's behavior
> described in 3 above expected?
no, it indicates you have something messed up on your end.
turn uugetty off and get uucp working first.
--
---------- Vince Skahan --------- vince@victrola.wa.com -------------
It'll be great fun for the whole family...with a firearms orientation
- incredible advertisement for local outdoors show.