FS#45228 - [bind] Removing bind package will make pwck fail
Attached to Project:
Arch Linux
Opened by Philipp M (bo0ts) - Saturday, 06 June 2015, 10:40 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 01 July 2015, 07:03 GMT
Opened by Philipp M (bo0ts) - Saturday, 06 June 2015, 10:40 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 01 July 2015, 07:03 GMT
|
Details
Description:
Installing and removing bind will make pwck and the shadow.service unit will fail with the following status: ● shadow.service - Verify integrity of password and group files Loaded: loaded (/usr/lib/systemd/system/shadow.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2015-06-06 12:28:18 CEST; 7min ago Process: 316 ExecStart=/usr/bin/pwck -r (code=exited, status=2) Main PID: 316 (code=exited, status=2) Jun 06 12:28:17 determinist systemd[1]: Starting Verify integrity of password and group files... Jun 06 12:28:18 determinist pwck[316]: user 'named': directory '/var/named' does not exist Jun 06 12:28:18 determinist pwck[316]: pwck: no changes Jun 06 12:28:18 determinist systemd[1]: shadow.service: main process exited, code=exited, status=2/INVALIDARGUMENT Jun 06 12:28:18 determinist systemd[1]: Failed to start Verify integrity of password and group files. Jun 06 12:28:18 determinist systemd[1]: Unit shadow.service entered failed state. Jun 06 12:28:18 determinist systemd[1]: shadow.service failed. This is caused by the following line in passwd: named:x:40:40:BIND DNS Server:/var/named:/sbin/nologin I'm not sure what the recommended behaviour is for packages that add new users. Should they remove them again on uninstall or just print a warning that a certain user is not needed anymore? Steps to reproduce: * # pacman -S bind && pacman -Rn bind * # pwck |
This task depends upon
Comment by Philipp M (bo0ts) -
Monday, 08 June 2015, 06:48 GMT
Comment by
Sébastien Luttringer (seblu) -
Thursday, 11 June 2015, 23:25 GMT
So, according to the related task pacman shouldn't touch users,
but I don't think the reason given applies if there are no files
by the user left behind.
I removed home directory for bind user, so it should be fixed in
bind-9.10.2.P1-1 (in testing for now)