You declaring a debt isn’t meaningful because you don’t have legal authority to do so.

A licence statement is describing in what way you’re granting permission for something you do have the right to control, which makes it meaningful

Nah, we’re alright. I don’t think anyone has clearly defined the requirements of earth citizenship, we can assume it’s like Ireland who hand it out like candy

No it wouldn’t. Whoever touched it last is responsible for it, that’s entirely consistent with the metaphore

I’m pretty sure it means exactly what it says, but you lot are all misreading it.

I interpret it as “all rights, except the right to commit, are reserved” (which doesn’t mean you surrender the right to commit, but rather that it’s the only right you aren’t depriving everyone else of)

The default is as long as it is because most people value not losing data, or avoiding corruption, or generally preserving the proper functioning of software on their machine, over 90 seconds during which they could simply walk away.

Especially when those 90 seconds only even come up when something isn’t right.

If you feel that strongly that you’d rather let something malfunction, then you’re entirely at liberty to change the configuration. You don’t have to accept the design decisions of the package maintainers if you really want to do something differently.

Also, if you’re that set against investigating why your system isn’t behaving the way you expect, then what the hell are you doing running arch? Half the point of that distro is that you get the bleeding edge of everything, and you’re expected to maintain your own damn system

The question you should be asking is what’s wrong with that job which is causing it to run for long enough that the timeout has to kill it.

Systemd isn’t the problem here, all it’s doing is making it easy to find out what process is slowing down your shutdown, and making sure it doesn’t stall forever

I find it makes my life easier, personally, because I can set up and tear down environments I’m playing with easily.

As for your user & permissions concern, are you aware that docker these days can be configured to map “root” in the container to a different user? Personally I prefer to use podman though, which doesn’t have that problem to begin with

Podman supports docker compose just fine. You have to run it as a service, so that it can expose a socket like docker does, but it supports doing exactly that

Because a container is only as isolated from the host as you want it to be.

Suppose you run a container and mount the entire filesystem into it. If that container is running as root, it can then read and write anything it likes (including password databases and /etc/sudo)