I found this

Quick Tip:

There are jokes you tell to your best buddies that you should never tell your boss.

Just saying : |

Found a bug today that made me groan in frustration.

It appears that the official elasticsearch debian package checks if the system's init daemon is systemd by... Checking if systemctl binary is available.

Issue is... Systems might contain that binary while using a different init, as the binary is part of the "systemd" package.

To actually switch to systemd however, the package systemd-sysv has to be installed, which creates a link from /bin/init to systemd's main executable.

What happens when your system doesnt use systemd then? The postinstall/preremove scripts fail as systemctl fails to talk to the system bus, and thus, the installation is marked as failed!

Oversights like this are exactly the reason behind my systemd dislike. We never wanted the systemd package, but another key package suddenly added it as a dependency one day...

Now to see if this is reported as a bug already, and if not, to report it myself...

(also, who checks for init by looking for the init's management utility?! Its like I checked if sysvinit is installed by checking if update-rc.d is installed!
And not like figuring out the system's init daemon is hard anyway! Just check /bin/init, or, better yet, check for process with pid 0!)

> systemctl enable --user pocketbase
> Failed to enable unit: Unit file pocketbase.service does not exist.

> Cat into ~/.config/systemd/user/pocketbase.service
> File exists.

Thanks for confirming you are shit systemd. I would love to see this happen in OpenRC or any sysv-like rc for that matter.

Fucking morons on a stick