automount locking

automount locking

Post by Peter Maurice-Jon » Thu, 18 Aug 1994 16:26:09


On our solaris 2.3 machine I keep getting the following messages :

Aug 16 17:00:07 solar automountd[1462]: No network locking on bear : contact admin to install server change

where "bear" is running 4.1.3

and "solar" is runing 2.3

Please could someone point me our whats happening here and if I can do
anything about it .



1. automount: no network locking on host question

Hello -

thanks to the FAQ, I'm able to have a better understanding as to why
I get the constant message to the console "automountd: No network locking
on host: etc..."

I followup question to this.  Would the detection of this condition,
and the display of the message of the console, significantly slow things
down, as the automounter goes about its business?  When changing directories,
or accessing a server on that same host, it seems like an unreasonable
amount of time passes, the evil message is blurted to the console, and then
what ever service I requested of the NFS server completes.

thanks for any insights you can give.  I'm running 2.3 on a Sparc 10.

        -- Todd

2. HELP needed to set up rsh for root of another machine

3. netscape rpm from compaq + my box = lock lock lock

4. compiling KDevelop

5. Modem TX and RX status via Num Lock-Caps Lock-Scroll Lock

6. PANIC! Need WordPerfect for SCO!

7. automount reading sun's automount file or NIS map


9. automount needs automount?

10. unable to lock mailbox: no locks available

11. More mail file locking questions (lockf, NFS, /var/spool/mail/*.lock)

12. Locking mechanisms / fcntl.c locks.c

13. XScreenSaver lock -> lock console