Xref: utzoo comp.mail.uucp:1413 comp.unix.questions:7863 Path: utzoo!attcan!uunet!oddjob!uwvax!vanvleck!uwmcsd1!mailrus!tut.cis.ohio-state.edu!osu-cis!dsacg1!dsacg3!ntm1569 From: ntm1569@dsacg3.UUCP (Jeff Roth) Newsgroups: comp.mail.uucp,comp.unix.questions Subject: Re: UUCP Over TCP/IP Message-ID: <908@dsacg3.UUCP> Date: 30 Jun 88 12:56:05 GMT References: <10036@marduk.uucp> Distribution: all Organization: Defense Logistics Agency Systems Automation Center, Columbus Lines: 24 From article <10036@marduk.uucp>, by gww@marduk.uucp (Gary Winiger): [responding to mparker@chip.UUCP's question on the TCP/IP UUCP service] > Page 2 of L.sys(5) in the 4.3BSD documentation documents a ``caller'' > field value of TCP. That will cause the sender's 4.3BSD UUCP system to > open a TCP connetion to the receiver's uucpd. The receiver, of course, > needs to have configured access to uucpd. I don't happen to have a 4.3 > system on hand configured that way to tell you what the inetd.conf line > has to look like, but I recall it all being in the source directories > for uucp. (If it isn't already configured.) from our /etc/inetd.conf: uucpd stream tcp nowait uucp /etc/uucpd uucpd from our /etc/services: uucp 540/tcp uucpd # uucp daemon from our /usr/lib/uucp/L.sys: dsacg1 Any TCP uucp dsacg1 ogin:--ogin:--ogin: Udsacg3 ssword: PASSWORD -- Jeff Roth (osu-cis!dsacg1!jroth) 614-238-9421 (Autovon 850-9421) From the Internet: jroth%dsacg1.uucp@daitc.arpa US Defense Logistics Agency Systems Automation I speak for myself Center, DSAC-TMP, Box 1605, Columbus, OH 43216