Hi, On zaterdag 30 juli 2022 16:46:57 CEST Chris Hofstaedtler wrote: > * Diederik de Haas <didi.deb...@cknow.org> [220730 15:12]: > > adduser: Warning: The home dir /run/uuidd you specified can't be accessed: > > No such file or directory Adding system user `uuidd' (UID 113) ... > > Adding new user `uuidd' (UID 113) with group `uuidd' ... > > Right. Not sure if we can suppress the warning.
>From https://wiki.debian.org/ReleaseGoals/RunDirectory: "/run is a new cross-distribution location for the storage of transient state files [...] which does not require preserving across reboots." My first thought was that /run/ was possibly an inappropriate directory for a home directory, till I found others do it too (and also remember a warning wrt pulseaudio about using /var/run instead of /run). I can create a directory in /run as root, so it doesn't seem to be a permission issue. Maybe it's a check within 'adduser' which generates the warning and prevents the creation of /run/uuidd ? Looking for other (system) user accounts with also a homedir in /run/ and found: https://salsa.debian.org/pulseaudio-team/pulseaudio/-/blob/master/debian/pulseaudio.postinst It uses a '--quiet' parameter, which may suppress the warning? > uuidd.socket listens on /run/uuidd/request, so thats automatically > created by systemd. > > The warning is only shown on first install, as the user then > remains on the system, even if uuid-runtime is purged. One way of > fixing this would probably be switching to DynamicUser. Not (very) knowledgeable about systemd, so can't comment on that. But if it can work also outside systemd, I'd prefer it. I'm fine if you want to close the bug as it is minor indeed :-) Cheers, Diederik
signature.asc
Description: This is a digitally signed message part.
