On Mon, 10 May 2004, Joseph Mack NA3T wrote: > On Mon, 10 May 2004, Ian Kent wrote: > > > > machine that does autoexpire nested nfs mounts > > > > > > < > Kernel automounter support > > > <M> Kernel automounter version 4 support (also supports v3) > > > > Yes. It loads the autofs4 module. > > > > > > > > machine that doesn't autoexpire nested nfs mounts > > > > > > <M> Kernel automounter support > > > <M> Kernel automounter version 4 support (also supports v3) > > Looked at the kernel config help for these options to find that you don't > activate the first option if you want autofs v3 or v4 support. Since the > question is simple, and knew I wanted autofs support, it never occured to > me to read the help. I just said yes to the first option. I didn't know > what the first line did or why there were two lines for autofs. Perhaps I > thought that the first line was core autofs code while the 2nd line was > for v3 and v4. > > Here's a suggestion for a fix > > < > Kernel automounter version 1,2 support (incompatible with v3,4) > < > Kernel automounter version 3,4 support >
That's not right. The first option is autofs (aka v3). As far as I'm aware both should work with basic functionality. > > Using autofs-4.0.0 you need to add > > > > alias autofs autofs4 > > > > to your modules.conf to ensure that autofs4 gets loaded. > > autofs4 was loaded 4.1.0 and above should automatically load the v4 module unless the v3 module is already loaded. > > > I wasn't aware expire didn't work with the autofs module and v4. > > If you have the first option activated in the kernel config > then > expire with _nested_ nfs mounts doesn't work > automount from autofs-4.1.2 won't load (well, loads and exits) > automount from autofs-4.0.0pre10 loads OK > expire with non-nested mounts works fine > fi autofs-4.0.0-1 was my first release. It added some fixes for submounts. pre10 was always a pre-release. With autofs-4.1.2 add a -d to the master map line and send the log fragment. > > > > I can't get the automount from autofs-4.1.2 to load on the machine which > > > doesn't autoexpire. automount runs and exits with no process in the ps table, > > > no errors in the logs. Running with -d gives a few lines in the log files > > > as it fires up, but no error messages. firing up the demon under strace, > > > looks the same in both cases, as I don't see anything after the fork(). > > > > Are you actually sending the *.debug to the log? > > I was looking in the wrong spot. autofs-4.0.0pre10 on my machine sends the > logs to a file called debug (don't have machine here, so I don't know > what's in syslogd.conf). I expected the logs from autofs-4.1.2 to go to > the same file, but it's being sent to the file "messages". So I found > the output now. Depends on your syslog config. Different severities may go to different locations. Unless you add either -v or -d to the master map line you shouldn't see much output. What is in your master map then? And the map your trying to load? Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
