On 3/1/19 5:53 PM, Gian Carlo wrote: > Il 01/03/19 22:40, riveravaldez ha scritto: >> Hi, I'm on debian-testing (updated), and found this issue: >> >> $ systemctl reboot >> Failed to set wall message, ignoring: The name >> org.freedesktop.PolicyKit1 was not provided by any .service files >> Failed to reboot system via logind: The name >> org.freedesktop.PolicyKit1 was not provided by any .service files >> Failed to start reboot.target: The name org.freedesktop.PolicyKit1 was >> not provided by any .service files >> See system logs and 'systemctl status reboot.target' for details. >> >> $ systemctl status reboot.target >> reboot.target - Reboot >> Loaded: loaded (/lib/systemd/system/reboot.target; disabled; vendor >> preset: enabled) >> Active: inactive (dead) >> Docs: man:systemd.special(7) >> >> $ systemctl restart reboot.target >> Failed to restart reboot.target: The name org.freedesktop.PolicyKit1 >> was not provided by any .service files >> See system logs and 'systemctl status reboot.target' for details. >> >> But 'sudo reboot' worked. >> >> Any idea? > > >> $ systemctl reboot >> $ systemctl status reboot.target >> $ systemctl restart reboot.target > You are NOT root > >> But 'sudo reboot' worked. > After "sudo..." you are root > > Bye, > > gc > >
I'm curious as to why $ systemctl restart reboot.target is being used. On my systems $ systemctl start reboot.target results in a request for the root password. (And results for failure to type it correctly for a remote system via SSH often gets you punished with a non-responsive SSH session on the terminal.) Am I misunderstanding the problem?
