make-automaps: Not run during startup if `/etc/automount/auto.scratch` exists

[pmenzel]

mxtools/make-automaps/make-automaps.service

Line 4 in 3a8210a

ConditionPathExists=!/etc/automount/auto.scratch

If a system is turned off, and a new user is created in the mean time, the user cannot log in, as the entry is missing in /etc/automount/auto.home. sudo /usr/sbin/make-automaps fixed it after a pdist.

@hyrulecastle:~$ sudo journalctl -b -u make-automaps.service
Aug 27 09:48:15 hyrulecastle.molgen.mpg.de systemd[1]: make-automaps.service skipped, unmet condition check ConditionPathExists=!/etc/automount/auto.scratch

[donald]

Hmm, I don't understand, why a user is in /etc/passwd but not in /etc/automount/auto.home. make-automaps.service at boot time should not be required. When a new user is created, clusterd pushes /etc/passwd, /etc/amd/amd.home and tells the system to create /etc/automount/auto.home from /etc/amd/amd.home. This all happens in a short time frame. There are theoretical race conditions (e.g. system going down before make-automaps completed) but I don't think they are likely to happen in real.

[pmenzel]

1. afk: Wed Aug 26 11:53:35 2026 +0200: mkuseracc elkonin # hyrulecastle ist aus
2. deinemuddah: 2026-08-26T14:56:39.054136+02:00 deinemuddah sudo: pmenzel : TTY=pts/0 ; PWD=/home/pmenzel ; USER=root ; COMMAND=/usr/local/bin/pdist push --set-pdist-status hyrulecastle

/etc/passwd was probably dist’ed then.

[donald]

/etc/passwd was probably dist’ed then.

Ah, that explains it. deinemuddah was updated when the user was created, hyrulecastle was dead at that time. The pdist updates /etc/passwd, /etc/amd/ but not /etc/automount/ (excluded via /root/Distfile).