Subject: Bug#4330: amd hangs system

From: Tim Wadsworth <[email-masked]>
Date: Thu, 29 Aug 1996 11:22:40 +0100

Package: amd
Version: upl102-3

Hi,

I am running the amd ("The 4.4BSD automounter") under Debian Linux
to mount users' home directories (and other shared filesystems).

The problem is that certain filesystems cause amd to lock up the
system, whereas mounting them using "mount" works fine. Other
filesystems work without any problems.

Amd appears to fork - presumably the child process attempts to perform 
the mount. Killing the "login" process, and the child "amd" process 
allows the system to run normally again, but attempting to access the 
same automount point again causes the behaviour to be repeated.
Any attempt to access any automount points from a shell just hangs the
shell (CTRL-C doesn't even get the prompt back).

The log messages do not shed any light on the problem. Eventually a
"fileserver xxx not responding still trying" appears, but the
fileserver itself is actually fine.

I'm using Debian 1.1, 2.0.0 kernel, libc.so.5.2.18

Amd is also used here on SunOS 4.1.3 and Solaris, and works without
this problem. I am using a direct copy of the map files.

The same problem occurs using Slackware and RedHat Linux and on 
different hardware. 

TIm.

---

From: Richard Kaszeta <[email-masked]>
Date: Thu, 29 Aug 1996 08:29:44 -0500

>The same problem occurs using Slackware and RedHat Linux and on 

Would you be willing to try another amd package?  To solve local
problems here I hand-patched a few things in the amd package, and
rolled in a few other patched from various newsgroups, and it has
worked without error for a month.

http://www.menet.umn.edu/~kaszeta/amd-upl102-custom1.i386.deb

*Please* let me know if you use it, and whether it works or not.

(Warning, it's config is a little different from the other amd packages).

-- 
Richard W Kaszeta 			Graduate Student/Sysadmin
[email-masked]			University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta