Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!mtune!jhc
From: jhc@mtune.ATT.COM (Jonathan Clark)
Newsgroups: comp.unix.questions
Subject: Re: Hostname aliasing in HDB UUCP
Message-ID: <1160@mtune.ATT.COM>
Date: Thu, 27-Aug-87 12:55:22 EDT
Article-I.D.: mtune.1160
Posted: Thu Aug 27 12:55:22 1987
Date-Received: Sat, 29-Aug-87 09:59:15 EDT
References: <623@quacky.UUCP>
Reply-To: jhc@mtune.UUCP (Jonathan Clark)
Organization: AT&T ISL Middletown NJ USA
Lines: 44

In article <623@quacky.UUCP> dce@mips.UUCP (David Elliott) writes:
>The situation is that system X wants to talk to system Y, while
>calling it Z.
>
>That is, the Systems file entry looks like:
>
>	hp-cup Any ...
>
>but the machine on the other side is actually named 'hpda'.

If I understand the problem correctly, you want to call hpda and have it
claim that it is hp-cup. If so, then the solution is as follows:

hpda's Systems entry is:

hpda Any ACU 4321 in: nuucp

hp-cup's entry is:

hp-cup Any ACU 4321 in: luucp

Note the different lognames.

Then in hpda's Permissions file you put:

LOGNAME=luucp MYNAME=hp-cup

and away you go.

This is in Appendix IV of my UUCP Administration manual, I have no idea
where it might be in the printed ones. You can also change your name while
calling out:

MACHINE=foo MYNAME=bar

makes your system claim to be 'bar' only when calling 'foo'.

Note that all this makes the *real* identity of the machine calling in
problematical at best...
-- 
Jonathan Clark
[NAC,attmail]!mtune!jhc

An Englishman never enjoys himself except for some noble purpose.