Return to BSD News archive
Xref: sserve comp.sys.sun.misc:11883 comp.sys.sun.admin:24931 alt.sys.sun:8507 comp.unix.bsd:13343 comp.unix.admin:16802 Newsgroups: comp.sys.sun.misc,comp.sys.sun.admin,alt.sys.sun,comp.unix.bsd,comp.unix.admin Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!usenet.coe.montana.edu!grapevine.lcs.mit.edu!olivea!sgigate.sgi.com!sgiblab!swrinde!cs.utexas.edu!howland.reston.ans.net!agate!dog.ee.lbl.gov!newshub.nosc.mil!nosc!pegasus!isle!bud From: bud@isle.pegasus.com (Bud Carlson) Subject: Re: Help with NIS Sun munged by 'hostname' .. _PLEASE_ Message-ID: <1994Jan24.210107.5772@isle.pegasus.com> Organization: Quantum Reef Project (Big Island of Hawaii) References: <1994Jan11.163433.26795@mnemosyne.cs.du.edu> <1994Jan18.212020.23383@kronos.arc.nasa.gov> Date: Mon, 24 Jan 1994 21:01:07 GMT Lines: 46 ken@kronos.arc.nasa.gov (Kenneth H. Simpson) wrote: >In article <1994Jan11.163433.26795@mnemosyne.cs.du.edu> croten@nyx.cs.du.edu (Charles Roten) writes: >>A problem recently arose on a Sun 386i, running SunOS 4.0.2, belonging to >>a friend of mine. His girlfriend was doing some work on it, running as >>'root'. She inadvertantly used the 'hostname' command to change the name >>of the workstation. The syntax, as best as she could recall, was >> >> hostname chenxi >> >>No problems were seen until the workstation was rebooted. By default, Sun >>386i's run Yellow Pages (NIS). And her mistake caused NIS to go bug- >>whacky and fail to reboot in multi-user mode. The problem surfaced during >>the loading of the YP daemons. The error message was >> >> yp server not responding for domain "YP.noname"; still trying >> >>Now, I have a similar machine, and I have his system disk mounted as my >>system's auxiliary disk. Hence, I can edit any file on his system disk >>to remove the corruption. I know his original system's name. Now for >>the big question. >> >>What file(s) did 'hostname' modify ??? I first checked /etc/rc.local. No >>soap. Then I did a 'grep -e chenxi *' in /etc. No soap. Where in the >>heck did 'hostname chenxi' do its dirty work ?!?!? >> > >The hostname should be set in > > /etc/hostname.le0 > >or something similar - perhaps hostname.ie0. Try reading the man page for unconfigure. It will explain and list all of the files affected by a host. The file that contains the hostname on a 386i is in the /etc directory but it's name is net.conf. To force the plug and play mechanism on boot-up you can stuff the string MUST_CONFIG on the first line of the file. Otherwise the file should be intuitive. Be careful if you do decide to use the unconfigure utility, it will delete home directories if you had them in the standard place for a 386i. .....Bud -- Bud Carlson * Manager * Big Island Technical Solutions * bud@isle.pegasus.com As far as we know, our computer has never had an undetected error. -- Weisert