InnerScientist @ InnerScientist @lemmy.world

Posts

1

Comments

324

Joined

2 yr. ago

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

metallb sounds like what you need, basicall you give it a range in your subnet (excluded from dhcp/Router!) and it assigns those ips to your loadbalancer services, it broadcasts this IP over Arp or bgp which makes automatic failover work.

The good within the bad

So, we're right on track?

Ping

You do backup important data, right?

Good to know

This one has reached the last stage, there's nothing that can be done.

The affliction is terminal.

No that comes afterwards

What do i do before I did that?

in the Gmail app on Android and iOS devices

At least it isn't my turn yet

Have you tried downloading more RAM?