Question on B class connecting to V class

[Chris Fadrowski]

I currently purchased a V 2500 with the control console B class 180L. Well, i am having a problem with the B class booting. It hangs at the NFS client on boot up. I was able to go into single user mode and change the nfsconf file using vi. However, it still hangs here on boot up and when i get back into the system, the nfsconf file is changed back to NFS_CLIENT=1 and NFS_SERVER=1 even though i changed it to "0". Why is it changing back and what is causing this? any ideas? I can't boot the system unless i use ctrl break. It's running HPUX 10.20.

[Pete Randall]

Chris,

Usually this ends up being some sort of name resolution issue. Has anything changed in this regard recently?

Pete

[Chris Fadrowski]

possibly the host name of the system. But i tried to change it when i received the system and it wouldn't let me so i don't think it has been successfully changed.

[Steven E. Protter]

I once hung a 9000 box on the nfs client step due to a typo in the file /etc/rc.config.d/netconf

I'm really, REALLY good at hanging 9000 boxes.

Just happened to the the first sensitive piece of software that hung. You symptons are similar but not exactly the same.

Can you bypass the nfs client step? Does the system continue to boot?

Steve

[Chris Fadrowski]

I'll tell you what.. i did get the system back by doing a make_recovery. It's very very possible that there was a typo in nfsconf. I tried using vi the first time on this file only to find out my term wasn't set to vt100 or hpterm and vi was all screwed up. I bet there were typo's in this file. If that can cause this, then i would bet this is the case.

[Pete Randall]

Chris,

I'd bet that was it. When the machine can't resolve it's own name, NFS (and other things) get downright testy.

Good luck,
Pete