HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS and Automounter Problem
Operating System - HP-UX
1833780
Members
2101
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 05:07 AM
05-29-2002 05:07 AM
NIS and Automounter Problem
We have recently converted the lab to a NIS configuration with Sun machines as the NIS Master and Slaves and a mixture of Sun and HP (HPUX 11.0) machines as the NIS Clients.
All seems to work well (so far) with one exception:
When logging onto the HP machines via the CDE as root, we see a problem when firing up the File Manager.
The File Manager seems to hang with "Reading..." in the status bar. In fact, the File Manager eventually recovers after about 40 mins and displays the filesystem. However, during this time users are unable to login via the CDE. Telnet sessions are OK, but NIS user home directories are not being auto-mounted.
If I try stopping and restarting nfs.client, I am told "cannot unmount /net : device busy".
If it helps, my /etc/auto_master file reads:
/net -hosts -nosuid,soft
I have tried changing the "timeo" and "retry" parameters, but it had no (noticeable) effect.
Thanks in advance.
All seems to work well (so far) with one exception:
When logging onto the HP machines via the CDE as root, we see a problem when firing up the File Manager.
The File Manager seems to hang with "Reading..." in the status bar. In fact, the File Manager eventually recovers after about 40 mins and displays the filesystem. However, during this time users are unable to login via the CDE. Telnet sessions are OK, but NIS user home directories are not being auto-mounted.
If I try stopping and restarting nfs.client, I am told "cannot unmount /net : device busy".
If it helps, my /etc/auto_master file reads:
/net -hosts -nosuid,soft
I have tried changing the "timeo" and "retry" parameters, but it had no (noticeable) effect.
Thanks in advance.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 08:42 AM
05-29-2002 08:42 AM
Re: NIS and Automounter Problem
Check the configuration for /etc/nsswitch.conf. I presume the user root, should be a local user on every system where the home directories would not be automounted. If so, then the configuration for /etc/nsswitch.conf should read :
passwd: files [NOTFOUND=continue]nis
group: files [NOTFOUND=continue]nis
hosts: nis [NOTFOUND=return] files
networks: nis [NOTFOUND=return] files
protocols: nis [NOTFOUND=return] files
rpc: nis [NOTFOUND=return] files
publickey: nis [NOTFOUND=return] files
netgroup: nis [NOTFOUND=return] files
automount: files nis
aliases: files nis
services: files nis
Also, double-check the automounter configuration for the master server:
# ypcat -k auto.master
which may or may not be the same as
/etc/auto_master
The nsswitch.conf entry would control
passwd: files [NOTFOUND=continue]nis
group: files [NOTFOUND=continue]nis
hosts: nis [NOTFOUND=return] files
networks: nis [NOTFOUND=return] files
protocols: nis [NOTFOUND=return] files
rpc: nis [NOTFOUND=return] files
publickey: nis [NOTFOUND=return] files
netgroup: nis [NOTFOUND=return] files
automount: files nis
aliases: files nis
services: files nis
Also, double-check the automounter configuration for the master server:
# ypcat -k auto.master
which may or may not be the same as
/etc/auto_master
The nsswitch.conf entry would control
Life is a promise, fulfill it!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 05:59 AM
05-30-2002 05:59 AM
Re: NIS and Automounter Problem
Thanks Corey.
I should have mentioned that we have tried various automount entries in the nsswitch.conf with no apparent effect.
For info, we have temporarily circumvented the problem with:
chmod 000 /usr/dt/bin/dtfile
Crude, but effective...
I should have mentioned that we have tried various automount entries in the nsswitch.conf with no apparent effect.
For info, we have temporarily circumvented the problem with:
chmod 000 /usr/dt/bin/dtfile
Crude, but effective...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2002 08:20 AM
05-30-2002 08:20 AM
Re: NIS and Automounter Problem
For starters, I have never had any success with an auto_master setup as you have. Mine is usually read
/net /etc/auto.home
/other /etc/auto.other
/- /etc/auto.direct
Order is important.
my auto.home is a "+auto.home" and the ypcat -k auto.home will show
* server:/big-disk/&
or something to that effect.
Next problem is that HP-UX does not use NFS version 3 by default. edit the file /etc/rc.config.d/nfs and change the AUTO_FS=0 to AUTO_FS=1 to force version 3 on the client.
Simply making the HP-UX systems use NFSv3 calls may fix your problem.
Regards,
Shannon
/net /etc/auto.home
/other /etc/auto.other
/- /etc/auto.direct
Order is important.
my auto.home is a "+auto.home" and the ypcat -k auto.home will show
* server:/big-disk/&
or something to that effect.
Next problem is that HP-UX does not use NFS version 3 by default. edit the file /etc/rc.config.d/nfs and change the AUTO_FS=0 to AUTO_FS=1 to force version 3 on the client.
Simply making the HP-UX systems use NFSv3 calls may fix your problem.
Regards,
Shannon
Microsoft. When do you want a virus today?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP