systemd 256 Nears Release With run0, systemd-vpick, importctl & More

[phoronix]

Phoronix: systemd 256 Nears Release With run0, systemd-vpick, importctl & More

It looks like systemd 256 will officially debut as stable in the near future with systemd 256-rc3 being released today and not tacking on any new features compared to the prior release candidates...

https://www.phoronix.com/news/systemd-256-rc3-Released

[jacob]

Hopefully we'll get this in Fedora 41

[mxan]

So when's systemd-kerneld coming?

[jacob]

So when's systemd-kerneld coming?

Its version 6.10 is currently in development.

[uid313]

I think systemd-oom is too low to react, when my system runs out of RAM it freezes for minutes before it kills the offending process.
And why let any process consume all remaining RAM? I would like to auto-kill any process that consumes more than 8 GB of RAM.

[Volta]

I think systemd-oom is too low to react, when my system runs out of RAM it freezes for minutes before it kills the offending process.
And why let any process consume all remaining RAM? I would like to auto-kill any process that consumes more than 8 GB of RAM.

You can change that limit (in Fedora it's unlimited for some reason, but it's probably related to cgroups). You can also run specific process with desired limits:

https://www.baeldung.com/linux/limit-resource-consumption

[uid313]

You can change that limit (in Fedora it's unlimited for some reason, but it's probably related to cgroups). You can also run specific process with desired limits:

https://www.baeldung.com/linux/limit...ce-consumption

It would be great if this was used by VS Code. I've ran my application within VS Code and then my computer froze and crashed because some infinite recursion due to a bug I had in my code that was used parsing or building some recursive tree structure.

[Volta]

It would be great if this was used by VS Code. I've ran my application within VS Code and then my computer froze and crashed because some infinite recursion due to a bug I had in my code that was used parsing or building some recursive tree structure.

Maybe you'll be able to tweak your VS run command and add limits there? Or try setting the limit for current user:

ulimit -Sv 1000000 (1GB for process)

[Avamander]

I think systemd-oom is too low to react, when my system runs out of RAM it freezes for minutes before it kills the offending process.
And why let any process consume all remaining RAM? I would like to auto-kill any process that consumes more than 8 GB of RAM.

Only a minute? The usual behaviour is total lock-up, especially if you've made the mistake of enabling swap on NVMe.

[uid313]

Only a minute? The usual behaviour is total lock-up, especially if you've made the mistake of enabling swap on NVMe.

Maybe two or three minutes.
I have a SATA SSD on a system with 16 GB RAM and I've disabled swap. I don't have any swap partition nor swap file.