% sudo /etc/init.d/dnsmasq restart
Restarting dnsmasq (via systemctl): dnsmasq.serviceJob for dnsmasq.service failed. See 'systemctl status dnsmasq.service' and 'journalctl -xn' for details.
failed!
% journalctl -xn
No journal files were found.
% sudo /etc/init.d/dnsmasq restart
Restarting dnsmasq (via systemctl): dnsmasq.serviceJob for dnsmasq.service failed. See 'systemctl status dnsmasq.service' and 'journalctl -xn' for details.
failed!
% journalctl -xn
No journal files were found.
With init, skipping a scheduled fsck during boot was easy, you just pressed
Ctrl+c, it was obvious! Today I was late for an online conference. I got
home, turned on my computer, and systemd decided it was time to run fsck on my
1TB hard drive. Ok, I just skip it, right? Well, Ctrl+c does not work, ESC
does not work, nothing seems to work. I Googled for an answer on my phone but
nothing. So, is there a mysterious set of commands they came up with to skip an
fsck or is it yet another flaw?
Увидел следующую замену systemd:
#define _XOPEN_SOURCE 700
#include <signal.h>
#include <unistd.h>
int main()
{
sigset_t set;
int status;
if (getpid() != 1) return 1;
sigfillset(&set);
sigprocmask(SIG_BLOCK, &set, 0);
if (fork()) for (;;) wait(&status);
sigprocmask(SIG_UNBLOCK, &set, 0);
setsid();
setpgid(0, 0);
return execve("/etc/rc", (char *[]){ "rc", 0 }, (char *[]){ 0 });
}
Какие подводные камни?