Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!HI-CSC.HONEYWELL.COM!bergstr
From: bergstr@HI-CSC.HONEYWELL.COM (-Darryl Bergstrom)
Newsgroups: comp.sys.apollo
Subject: Re: uuname -l, gethostname etc.
Message-ID: <9101031354.AA16774@heavyd.hi-csc.honeywell.com>
Date: 3 Jan 91 13:54:26 GMT
References: <189@raysnec.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

glass@SODA.BERKELEY.EDU writes:

>I have a machine with the hostname "soda.berkeley.edu" .  I'm trying
>to set it up so that it can do uucp but it thinks its "uuname -l" is
>"soda.Berkeley.".  The name is bad enough but the trailing dot breaks
>lots of stuff (mainly sendmail).  So how do I convince my machine that
>my uuname is really "soda"?  uuname in and of itself is relatively
>innocuous but uucico seems to have the same confusion.

Ray>	Well, soda.berkeley.edu may be your FQDN (fully qualified domain
Ray>name), but "uuname -l" should point only to your nodename. (Don't
Ray>know where apollo is pulling the name; often it's the kernel, or
Ray>/etc/sitename,or ....) Since "soda.Berkeley." comes to 14
characters, I Ray>would assume your system runs an HDB-like UUCP, which
recognizes Ray>only 14 character nodenames.

Ray>uuname in and of itself may be innocuous, but what it reveals is
Ray>not. If a site spools a request for "soda", and you come in and identify
Ray>yourself as "soda.Berkeley.", you will not be given that spooled request.

uucp looks at the file /usr/lib/uucp/sitename to determine the sitename.

Put soda in this file and all is done.

-darryl
bergstr@hi-csc.honeywell.com