After the 'systemctl start crashsystemd' my terminal says:
Failed to start crashsystemd.service: Connection reset by peer
See system logs and 'systemctl status crashsystemd.service' for details.
and in the systemd logs I see:
Jul 17 23:20:33 jturner-desktop systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting.
Things are pretty broken now. 'systemctl' and 'reboot' commands won't work. Don't forget to delete the /etc/systemd/system/crashsystemd.service symlink before rebooting.
Sorry, turns out the /etc/systemd/system service file needs to be a symlink to trigger the bug. This will do it:
su - .service Template for instance %i
cat <<EOF > /crashsystemd@
[Unit]
Description=
[Service]
ExecStart=/bin/true
EOF
cd /etc/systemd/system .service crashsystemd. service
ln -s /crashsystemd@
systemctl daemon-reload
systemctl start crashsystemd
After the 'systemctl start crashsystemd' my terminal says:
Failed to start crashsystemd. service: Connection reset by peer service' for details.
See system logs and 'systemctl status crashsystemd.
and in the systemd logs I see:
Jul 17 23:20:33 jturner-desktop systemd[1]: Assertion 'u->instance' failed at src/core/ load-fragment. c:4798, function unit_load_ fragment( ). Aborting.
Things are pretty broken now. 'systemctl' and 'reboot' commands won't work. Don't forget to delete the /etc/systemd/ system/ crashsystemd. service symlink before rebooting.