[Bug 290468] automountd writes its pidfile in a way which makes it fail to start on a netbooted system

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 24 Oct 2025 08:01:41 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290468

            Bug ID: 290468
           Summary: automountd writes its pidfile in a way which makes it
                    fail to start on a netbooted system
           Product: Base System
           Version: 14.3-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: d8zNeCFG@aon.at

Scenario:
- FreeBSD stable/15 i386 b339da5b23e8 plus minor local patches
- (amd64 is affected in the same way)
- in /etc/rc.conf, autofs_enable="YES"
- Netbooting using iPXE; the exported filesystem contains a complete FreeBSD
installation (see above) and is exported with -maproot=root:wheel:operator (via
zfs sharenfs)

Result:
- automountd creates /var/run/automountd.pid, but the file remains empty
- The following error messages appear:

Starting automountd.
automountd: cannot open or create pidfile "/var/run/automountd.pid": No locks
available
/etc/rc.d/automountd: WARNING: failed to start automountd

Expected result:
- autofs should also work on a netbooted machine

Notes:
- Until a while ago, this was more or less working. It did not work during the
boot sequence, but it was then possible to "service ... stop" the three
automount components and then start them correctly using "service ... start".
Now not even this method is working anymore.
- It is not even working if I manually remove the pidfile before trying to
restart the daemons.

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.