Am 21.09.2016 um 06:29 schrieb Michael Biebl: > Control: tags -1 moreinfo unreproducible > Control: severity -1 important > > Am 21.09.2016 um 05:31 schrieb Grond: >> Setting up systemd (215-17+deb8u5) ... >> addgroup: The group `systemd-journal' already exists as a system group. >> Exiting. >> dpkg: error processing package systemd (--configure): >> subprocess installed post-installation script returned error exit >> status 1 > > ... > >> `getent` queries for the other systemd users referenced in the above have >> similar results. >> Apparently, `adduser` returns a non-zero exit status when told to create a >> user that already >> exists, even if the --quiet flag is given. > > If that's the case, then this would be a bug in adduser and not systemd. > I can't reproduce that though > > # getent passwd systemd-timesync > systemd-timesync:x:108:113:systemd Time > Synchronization,,,:/run/systemd:/bin/false > > # adduser --quiet --system --group --no-create-home --home /run/systemd > --gecos "systemd Time Synchronization" systemd-timesync > > # echo $? > 0 > >> Since the whole script is run under `set -e`, when the `adduser` command >> fails, the entire >> systemd.postist script aborts. > > Can you add "set -e" to systemd.postinst and then run > dpkg --configure -a and attach the log. Somehow I suspect the addgroup / > adduser message is a red herring. >
Just to be sure, please run # adduser --system --group --no-create-home --home /run/systemd --gecos "systemd Time Synchronization" systemd-timesync # echo $? and attach the output -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
