==> Regarding [autofs] Debugging hung autofs /home?; Jim Davis <[EMAIL PROTECTED]> adds:
jdavis> [EMAIL PROTECTED] /]# ps ax | grep auto jdavis> 2709 ? Ss 0:00 /usr/sbin/automount --timeout=3600 --verbose jdavis> --debug /home file /etc/auto_home -rw,intr,nosuid jdavis> 2763 ? Ss 0:00 /usr/sbin/automount --timeout=3600 --verbose jdavis> --debug /cs file /etc/auto_cs -rw,intr,nosuid jdavis> 3776 ? S 0:00 kalarmd --autostart jdavis> 21284 pts/16 S+ 0:00 grep automount jdavis> 21827 pts/28 S+ 0:00 grep auto jdavis> [EMAIL PROTECTED] /]# kill -HUP 2709 jdavis> [EMAIL PROTECTED] /]# strace -f -p 2709 jdavis> Process 2709 attached - interrupt to quit jdavis> futex(0x2aaaaaefd840, FUTEX_WAIT, 2, NULL jdavis> That process doesn't respond to kill -HUP, USR1, USR2, or /sbin/service jdavis> autofs reload. (The other automount process associated with /cs seems jdavis> to be fine.) New mounts under /home just hang. Mounting the jdavis> directories by hand from the NFS server works. jdavis> This is on a 4-processor AMD system running FC4: jdavis> Linux lectura.cs.arizona.edu 2.6.14-1.1656_FC4smp #1 SMP Thu Jan 5 jdavis> 22:26:33 EST 2006 x86_64 x86_64 x86_64 GNU/Linux And you left off the version of autofs you're running. Most likely it's older, and does not have the reentrant syslog patches. I think an upgrade will fix your wagon. ;) -Jeff _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
