Manuel Giraud <man...@ledu-giraud.fr> writes: > Stuart Henderson <stu.li...@spacehopper.org> writes: > >> On 2025-06-16, Dave Voutila <d...@sisu.io> wrote: >>> Sonic <sonicsm...@gmail.com> writes: >>> >>>> After updating to the latest snapshot followed by updating packages >>>> sysclean is showing: >>>> ======================= >>>> # sysclean >>>> @user build:21:wobj::/var/empty:/bin/ksh (modified) >>>> ======================= >>>> What does that output mean and what action should be taken? >>>> >>> >>> There's an outdated user "build" no longer defined in the base >>> install. You can use userdel to remove it. >> >> Nearly but not quite - the user still exists but the master.passwd entry >> changed. This one (and if you see them, others with low uids, below 500) >> is from the base OS. >> >> You can userdel, but then run sysmerge afterwards and it will be readded >> with the new default passwd entry. > > Hi, > > I have the same issue as OP but also with packages' users. For example: > > # sysclean > @user _dbus:572:_dbus:daemon:/nonexistent:/sbin/nologin (modified) > @user _rsync:669:_rsync:daemon:/var/empty:/sbin/nologin (modified) > > In such case, the sysmerge after userdel does not readd said user. How > should I proceed then?
sysclean has a new check for looking at login class. the 'modified' entry means there is a mismatch between system install (or packages) and what is found locally the _dbus entry should be: _dbus:572:_dbus::dbus user:/nonexistent:/sbin/nologin (default login class, and not daemon) the _rsync entry should be: _rsync:669:_rsync::rsync Daemon:/var/empty:/sbin/nologin (default login class, and not daemon) it could be fixed by reseting the login class to '' $ doas user mod -L '' _dbus $ doas user mod -L '' _rsync Regards. -- Sebastien Marie
