Login
You're viewing the functional.cafe public feed.
  • Nov 17, 2026, 4:22 PM

    @ska I understand why this system must be architected the way it was architected, but that doesn't mean I had a fun day yesterday.

    One problem perhaps bigger than any particular interface decision is that the interface to my applications was changed out from under me without me even knowing it (I still don't know when systemd appeared on my system; it wasn't there when I installed Linux on this server, and one day it was)

    💬 1🔄 0⭐ 0

Replies

  • Nov 17, 2026, 7:31 PM

    @mcc Yeah, that branches into the "distros are shit at respecting users' time and habits" rant, which I totally agree with, but it's not my area of expertise (it's more @gro-tsen.bsky.social 's). I stuck to the part of your story that I could provide lighting for. 😅

    💬 1🔄 0⭐ 1
  • Nov 17, 2026, 10:27 PM

    @ska @mcc @gro-tsen.bsky.social I don't think I have any particular expertise to bring (other than thank you for an instructive thread), but as far as communicating user wishes, I believe it ought to be possible to start/stop/restart Apache either with `systemctl` or `apachectl`, and, moreover, they should interact completely harmoniously with each other. I'm not saying I know *how* this can be done, but it *should*.

    💬 2🔄 0⭐ 0
  • Nov 17, 2026, 10:30 PM

    @ska @mcc @gro-tsen.bsky.social … Because this is a problem that has repeatedly plagued the Linux ecosystem at large: you have N different tools that more or less accomplish the same task (here, `systemctl` and `apachectl`), and the user is completely confused as to how they relate or interact (are they synonyms? incompatible? is one obsolete?). Such mazes should always be resolved by harmonious interaction between the tools.

    💬 0🔄 0⭐ 0
  • Nov 17, 2026, 10:34 PM

    @gro_tsen_test @ska @gro-tsen.bsky.social Actually, it is *possible* that newer versions of apachectl do work this way; I am using a somewhat old LTS, on this one system.

    This said there is some design difficulty here because systemd does what it does by *invoking* apachectl, so we'd need something wacky like a --no-really-im-systemd argument to apachectl. It gets awkward.

    💬 0🔄 0⭐ 0