1830933 Members
1982 Online
110017 Solutions
New Discussion

Re: hpux Xwindow issue

 
anonymous_5
Occasional Advisor

hpux Xwindow issue

Xwindows wont start after I monkeyed ( broke) the NIS or name services .. I believe.

How do I prevent the xwindows from launching me into a garbage environment? How do I
break out of the garbage environment.

And what is the proper way to set up name service ( from sam) for a box running 11.0 hpux & hpov nnm in a lab environment.

Is there a best method when dealing with hpov nnm withrespect to name services.

I was wanting to configure the hpov nnm box as the primary domain server. Is this normal & a best practice?
6 REPLIES 6
Wodisch
Honored Contributor

Re: hpux Xwindow issue

Hi Jamie,

running a local DNS name server on your NNM station is always recommended - but NOT a primary/master!
As then your NNM station would be gogged down by the amount of DNS requests from all the other systems. No, you wouldn't want that. all you want is an autonomous name resolution, even if your company's DNS goes down, or is broken...
Make you NNM station become a DNS secondary/slave or just a cash/hint server - that's good enough. And make your NNM stations the only DNS client of that DNS server!
If your X/CDE was running before, you might have to delete the whole "$HOME/.dt/" subdirectory, as CDE uses that to remember things, including hostnames.

HTH,
Wodisch
anonymous_5
Occasional Advisor

Re: hpux Xwindow issue

ok, thanks for the dns advice... but I have more immediate issues with X. It was running, but now it is foo-ed because of dns issues.

How can I fix X ???
anonymous_5
Occasional Advisor

Re: hpux Xwindow issue

ok, thankyou for sending mail... but this is a lab box.

Anyway, I am only aware of how to change dns settings in the SAM. now that xwindows is not working how do I follow your suggestion and disable NIS. I checked resolv.conf & etc/ hosts. I believe NIS is causing the problem.

Please be more specific as to how I can fix my xwindows NIS issue. & thankyou very much...
Alex Glennie
Honored Contributor

Re: hpux Xwindow issue

I guess it depends upon the garbage,

will generally kill the Xserver provided it's not got itself into a busy or hung state at the local graohics console. CDE may respawn so you need to be quick at the login prompt.

Alternatively and if you can telnet into the box and run /usr/dt/bin/dtconfig -d to disable it may need a -k too see man page.

another method maybe to run /sbin/init.d/dtlogin.rc stop/start to prevent the demon running whilst you fix NIS.

Not sure what you mean by garbage enviroment ... I'd of expected CDE simply to have thrown you back out to the CDE login screen .... however I'd suggest you either fix NIS or run /usr/contrib/bin/X11/dr_dt (CDE diagnostic tool and also ammend /etc/nsswitch.conf to point to files first ensuring local ip address and short hostname entries are in /etc/hosts ... also ensure it has correct permission (dr_dt will check them).

Let us know how you get on and what kinda of garbage you have ;-)
anonymous_5
Occasional Advisor

Re: hpux Xwindow issue

ok, thanks alex. the usual break keys aren@t doing it, and the `garbage` is just a blank screen that doesn`t want to let break function... and occassionally when it does
x respawns. I suppose if I could edit the proper files in /etc while in single user mode that would be helpful.

while X was working I used SAM to enable the box as a prime server.

So then, what do I need to do in text mode to diable this function. Is it as simple as removing the nsswitch.config file?

anyway, i`m travelling in a future time zone so I`ll send you more later. perhaps... if I rm the nsswitch file that I created my issue will be resolved... and then I can check out some more docs on name services. ; - >
Alex Glennie
Honored Contributor

Re: hpux Xwindow issue

To disable NIS master from cmd line ->

/sbin/init.d/nis.server stop
/sbin/init.d/nis.client stop

vi /etc/rc.config.d/namesvrs accordingly
remove NIS entry from /etc/nsswitch.conf