On Thu, 2022-01-20 at 17:21 +0800, Ian Kent wrote: > On Thu, 2022-01-20 at 08:26 +0100, Fabian Groffen wrote: > > On 20-01-2022 10:37:20 +0800, Ian Kent wrote: > > > On Wed, 2022-01-19 at 18:55 +0100, Fabian Groffen wrote: > > > > I've applied all of the patches from your patchqueue, but I > > > > don't > > > > see > > > > much change. Startup only shows: > > > > > > > > Jan 19 18:53:20 hera automount[21763]: Starting automounter > > > > version > > > > 5.1.8, master map auto.master > > > > Jan 19 18:53:20 hera automount[21763]: using kernel protocol > > > > version > > > > 5.05 > > > > Jan 19 18:53:20 hera automount[21763]: lookup_nss_read_master: > > > > reading master files auto.master > > > > Jan 19 18:53:20 hera automount[21763]: do_init: parse(sun): > > > > init > > > > gathered global options: (null) > > > > Jan 19 18:53:20 hera automount[21763]: spawn_mount: mtab link > > > > detected, passing -n to mount > > > > Jan 19 18:53:20 hera automount[21763]: spawn_umount: mtab link > > > > detected, passing -n to mount > > > > Jan 19 18:53:20 hera automount[21763]: no mounts in table > > > > > > > > > This looks like output you would get if debug logging isn't > > > enabled. > > > > > > Are you using systemd or a sysV init system? > > > > sysv/openrc > > > > > Has the build log of autofs been checked for problems? > > > > yes, none present > > > > > Has the earlier version of autofs that you see working been built > > > against the same system? > > > > yes > > > > > We really need to get a debug log for this, can't really make > > > progress > > > otherwise. > > > > I enabled logging=debug (I use the same config) and 5.1.6 spews out > > a > > lot of messages that it normally does not, so I'm assuming that's > > what > > logging=debug does. The problem appears to be to me that 5.1.8 > > doesn't > > do this, so it seems to either not read /etc/autofs/autofs.conf, > > or auto.master/auto.net from the same directory? > > If it's not using the expected location for autofs.conf that's a > build > problem. > > Can you get me a build log. And what does "automount -V" say? Ian > > Ian > > > > Thanks, > > Fabian > > > > > > Ian > > > > > > > > Thanks, > > > > Fabian > > > > > > > > On 19-01-2022 09:27:26 +0800, Ian Kent wrote: > > > > > On Tue, 2022-01-18 at 11:27 +0100, Fabian Groffen wrote: > > > > > > On 18-01-2022 18:24:11 +0800, Ian Kent wrote: > > > > > > > A debug log is almost always what I ask for. > > > > > > > > > > > > > > Setting "logging = debug" in /etc/autofs.conf will do it. > > > > > > > You need to get a log from start of automount to after > > > > > > > the > > > > > > > problem > > > > > > > occurs. > > > > > > > > > > > > Let me try this and come back to you. > > > > > > > > > > You might need to take some care doing this. > > > > > > > > > > If your using systemd then a simple "journalctl | grep > > > > > automount" > > > > > usually gets what we need. > > > > > > > > > > But if your relying on syslog often the log level setting > > > > > won't > > > > > record debug logging so it needs to be changed. Otherwise we > > > > > don't > > > > > get a full log. > > > > > > > > > > Ian > > > > > > > > > > > > > > > > > >
