*Chooses "no, I don't respond to surveys"*
InnerScientist
joined 2 years ago
No matter what your stance on Trump is, you must agree that it isn't completely outside the realm of possibilities.
I wonder if anyone believed them at the time
And systemd requires notify about this intention every time.
Systemd requires a one time fee of loginctl enable-linger myserviceuser to never kill processes with a timeout for that user again. This behavior also doesn't affect system users, only normal users.
I think the main purpose nowadays is to stop pipewire and other user services that don't need to consume resources when that user isn't logged in
I think s6 may be newer
If you run screen/tmux built without systemd support, it will be killed on logout.
Actually, if you run anything and logout, it will be killed after a timeout. The way to prevent this in systemd land is to enable-linger for that user.
IMO this is a pretty sane default and it's easy enough to disable for users
EDIT: For non-root users
....you assumed correctly, runit first released 2004, meanwhile systemd released 2010
I'm talking about software RAID, for example btrfs.
Most RAID levels are for redundancy, not speed and software RAID doesn't need drives of the same size.
if one drive dies it's got a copy on another drive
Do you want JBOD or a RAID? Cause dealing with disk failure is a feature of RAID
I hate arch users btw
view more: next ›
The only way to completely fix it is to make the services be compatible, so that people can switch without the downside of leaving people behind.
This is complicated and has downsides though.