Re: Setting up UUCP over TCP
I have several uucp over TCP/IP connections and you do not even need the
service 540 entry, it defaults to 540, use the service entry if you are
connecting to a non-standard port.
> : 3. port:
> :
> : port tcp-conn
> : type tcp
> : service 540
> :
> : and that's it. The dial, dialcode and call files are unnecessary in
> : this case.
>
> Think so, but not for sure. /usr/lib/uuchk is a very helpful tool.
>
> : Here is where I start getting a bit confused. If this ran over
> : a modem line and was logged in using mgetty then life would be simple
> : in that the shell of the user would be set to uucico. When the user
> : logged in uucico would run and off they go. Over tcp there has to
>
> Right. Some systems use login names as ``Ulotte'' for the uucp logins
> (as ``Plotte'' for PPP and ``Slotte'' for SLIP). The shell for
> ``Ulotte'' would be uucico. IMHO getty passes the login name to uucio.
> (probably uucico needs some options (-l), thus you'll have to set up
> a litte script, calling uucico w/ the right options (as /etc/passwd
> doesn't allow options for the shell)). This is explained in uucico(8).
>
>
> : be a daemon listening to port 540. In one of the docs that I read
> : about uucp mentioned a uucpd that I couldn't find. In the man page
> : for uucico the -l or -e options makes uucico negotiate a login. Does
> : this mean that uucico will naturally listen to port 540? (It doesn't
>
> As far as I know -- no. uucico should be called via inetd.
>
> : seam likely to me.) The man page also says that the /etc/passwd file
> : is not used but instead /usr/lib/uucp/passwd. Are these files in the
> : same format and could the /etc/passwd file be copied to make the
> : /usr/lib/uucp/passwd file?
>
> This is a compile time option. (Better yet: was a compile time
> option when I had to deal with.) Normally uucico performs a simple
> look up in it's own password data base, there are not even crypted
> passwords -- again, AFAIK. I felt look-up's in /etc/passwd much better
> -- because of security and because I didn't want to maintain just
> another password file. At least an strace should show you the file
> uucico expects.
>
>
> : I think that this is about it for now. Sorry about the bother
> : but it seams that most of the references to uucp are related to
> : dialup lines and tcp is usually only mentioned as an after thought.
>
> UUCP (Taylor UUCP) is accompanied with a very comprehensive/detailed
> description of it's options. (Although some UUCP basics are useful to
> understand this doc. I'd recommend O'Reilly's _Managing_ UUCP and
> Usenet -- but your questions show that you probably read this book ;-)
> yet)
>
> : It seams to me that uucp is the ideal way to move mail or news when a
> : host is not on all the time and only comes on to gather it's
> : information then get off in a polling cycle instead of being poled.
>
> Yes. It should be the choice for all these non permanently connected
> sites --- but it seems, that it's often considered as ancient, ISP don't
> like or don't know it, and customers never heard about it :-(
>
>
>
> Heiko
> --
> email : heiko@lotte.sax.de heiko@debian.org heiko@sax.de
> pgp : A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92
> finger: heiko@sax.sax.de heiko@debian.org
>
George Bonser
grep@oriole.sbay.org, grep@concentric.net
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: