💾 Archived View for tozip.chickenkiller.com › 2022-05-27-systemd-bullshit.gmi captured on 2023-03-20 at 17:55:45. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

systemd is bullshit

Created 2022-05-27

A rant.

So anyway, I decide to set up a gopher server on Debian Stable.

Fine, it installs. OK, so now where are the logs, where's

the route directory. And come to think of it, what is the

process called?

Time to peel away the onion layers that is systemd. So, it

turns out that to get a clue as to what's going on, I should

type

systemctl list-units | grep gopher

yielding:

system-gophernicus.slice

loaded active active system-gophernicus.slice

gophernicus.socket

loaded active listening Gophernicus gopher server

So, that's two things going on. Where's the log?

Try typing :

journalctl system-gophernicus.slice

is wrong, gotta type:

journalctl -u system-gophernicus.slice

Good guess. It yields lines like:

May 27 11:38:43 blinkyshark gophernicus[8784]: request for "gopher://blinkyshar>

Now the line is truncated to the width of the terminal. Sigh. So widen the terminal,

and try again. Success.

Systemd is a hideous mess of make-work. I don't understand

how anyone can rate it. It's got me seriously contemplating

trying out Slackware or one of the BSDs on a Raspberry Pi. Fingers crossed

on getting wifi working though.

In Slackware, if I want to start something up I can just put

it in /etc/rc.local. I don't have to faff around with services

or any of that nonsense. It's sooooooo easy.