Nalin Dahyabhai wrote: > On Mon, Dec 03, 2001 at 09:20:24AM +0100, Heinrich Rebehn wrote: > >>Anyway, is there any way to have autofs run in the foreground an output its >>error messages to stdout, so i can see what autofs is really trying to mount? >>There's nothing written into syslog. >> > > The module logs quite a bit of information at the "debug" priority, so > adding a line like this to /etc/syslog.conf and restarting syslogd > should give you more information: > > *.debug /var/log/debug > > HTH, > > Nalin >
I think i have already setup syslog this way, because with successfull autofs mounts i get messages like: Dec 3 17:55:20 oslo automount[235]: attempting to mount entry /ant/www Dec 3 17:55:20 oslo automount[12759]: lookup(yp): looking up www Dec 3 17:55:20 oslo automount[12759]: lookup(yp): www -> antsrv1:/export/data/www Dec 3 17:55:20 oslo automount[12759]: expanded entry: antsrv1:/export/data/www Dec 3 17:55:20 oslo automount[12759]: parse(sun): core of entry: antsrv1:/export/data/www Dec 3 17:55:20 oslo automount[12759]: mount(nfs): calling mkdir /ant/www Dec 3 17:55:20 oslo automount[12759]: mount(nfs): calling mount -t nfs antsrv1:/export/data/www /ant/www Dec 3 17:55:20 oslo automount[12759]: mount(nfs): mounted antsrv1:/export/data/www on /ant/www The problem seems to be, that in the "crash case" the logging information is not written to file fast enough. I will try logging to an external machine. Anyway, a "foreground" option would be quite helpful and many other daemons come with that. Heinrich
