Arch Linux

Lekensteyn

Member

From: Netherlands

Registered: 2012-06-19

Posts: 192

Website

[SOLVED] `systemctl restart systemd-tmpfiles.d-setup` broke sudo

I created some file in /etc/tmpfiles.d/foo.conf in order to create a temporary directory in /run. It did not appear when I saved the file (no inotify? tsk), so I decided to restart the service which is responsible for it (I guess):

systemctl restart systemd-tmpfiles.d-setup

Now every time I try to run a sudo command, I get:

$ sudo ls
[sudo] password for peter: 
System is booting up.
Sorry, try again.

The password is correct for sure. When I run "runlevel", it says "unknown" instead of "N 5". (this "System is booting up" error looks like https://bbs.archlinux.org/viewtopic.php?id=146376)

What the f*ck, systemd? How can I fix this without rebooting? I tried "telinit 5", but got a permission error...

Edit: I got "runlevel" telling "N 5" now after running "systemctl isolate graphical.target" as root (through a root vim which was already open, heh). But sudo is still broken with the same error. It was working correctly because I restarted this crappy systemd program.

Edit: it turns out that systemd-tmpfiles.d also creates /run/nologin which breaks pam or sth...

Last edited by Lekensteyn (2012-12-27 17:22:30)