Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!aplcomm!uunet!cs.dal.ca!silvert
From: silvert@cs.dal.ca (Bill Silvert)
Newsgroups: comp.sys.sgi
Subject: Re: Name Server problem
Summary: Problem solved
Message-ID: <1991Jun19.150928.19282@cs.dal.ca>
Date: 19 Jun 91 15:09:28 GMT
References: <1991Jun18.203401.24264@cs.dal.ca> <9106191246.AA29392@ccfiris.aedc>
Sender: silvert@cs.dal.ca.UUCP (Bill Silvert)
Reply-To: silvert%biome@cs.dal.ca
Organization: Habitat Ecology Div., Bedford Inst. of Oceanography
Lines: 27

In article <9106191246.AA29392@ccfiris.aedc> mcdonald@AEDC-VAX.AF.MIL writes:
>In response to Bill Silvert:
>>> you can put the PI's name in /etc/sys_id as PIname.domain.name.
>>>This should solve your problem.
>>
>>I've tried both.  The solution doesn't work.  
>
>You can do this by having the name in /etc/sys_id & then doing 1 of the
>following:
>   - reboot for this name to take effect.
>   - use the hostname command to set you hostname:
>       % hostname name.domain.name
>     (if you use this second method you may have to reload named ?)
>This method works fine for us.

Thanks.  Several people suggested modifying /etc/sys_id, but I hadn't
realized that it didn't have any immediate effect.  So I used the
hostname method (a bit less drastic than rebooting!) and all is OK.
I can also use the System Manager again for networking.

Goes to show that when advising novices you may have to include the
stupid little bits that "everybody knows"!
-- 
William Silvert, Habitat Ecology Division, Bedford Inst. of Oceanography
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2.  Tel. (902)426-1577
UUCP=..!{uunet|watmath}!dalcs!biome!silvert
BITNET=silvert%biome%dalcs@dalac	InterNet=silvert%biome@cs.dal.ca