Saturday, May 09, 2015

Don't use systemd

Upgraded to jessie.  On reboot;

* primary network interface is not configured.  This caused total network outage as this system is the DHCP server for the network.  Root cause = systemd.  It messed up the network config.

* Full GUI loads at boot.  RPi was set to be headless, but systemd pulled in dependencies requiring all of X11 (probably for the hideously awful systemd-ui app, the most user-unfriendly thing I've used.  And I've used Microsoft Windows.)

* systemd-logind is broken by default, there's no login consoles.

* load is constantly over 1.5 because of this:

top - 15:21:53 up 4 days,  2:12,  2 users,  load average: 1.58, 1.58, 1.50
Tasks: 127 total,   2 running, 125 sleeping,   0 stopped,   0 zombie
%Cpu(s): 10.4 us, 14.2 sy,  0.0 ni, 75.2 id,  0.0 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem:    949408 total,   711404 used,   238004 free,    88224 buffers
KiB Swap:  1918972 total,        0 used,  1918972 free.   247176 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
    1 root      20   0    6416   4972   2748 R  77.6  0.5   4493:41 systemd


Hovers between 77 and 90% CPU utilisation.  There's absolutely NOTHING logged as to why.

* shutdown is broken because systemd refuses to shut the system down until one of its broken components responds - which it doesn't in 7 hours of waiting.  Only solution is hard poweroff.


Whoever decided this should be the default init in Debian needs to be taken out to pasture and shot thrice.