3 ms·
I mean there's always a way to configure/disable it, but a counter-argument would be that if there's an optimal solution to the OOM problem, I would prefer that
by Nextgrid 6y ago
I mean there's always a way to configure/disable it, but a counter-argument would be that if there's an optimal solution to the OOM problem, I would prefer that all distros use it.
Just like you can mostly expect filesystem behavior to be consistent no matter which distro, so should be the OOM behavior if a "good" solution is found.
- gmueckl 6y agoYou can't expect filesystem to behave consistently across filesystem and media types because these exist to solve different issues and involve different design decisions. The same thing goes for out of memory handling: no size fits all. The kind of handling strategy you need depends on the kind of system you build. Exactly this kind of flexibility and lack of unification is what made Linux so ubiquitous.
- kreetx 6y agoI think what the OP means is that you can be in any filesystem without needing to put much thought into it (regardless of the very real differences in implementation). Advanced users who want to interface with the details can do that, but for the rest of us consistency can be good.
- robertlagrant 6y agoIsn't the same level of detail needed for init as for different filesystems?
- gmueckl 6y agoExcept that file systems aren't consistent on Linux. FAT and NTFS can't represent Unix permission bits. File systems reorder operations internally in some ways user space programs don't expect. NFS mounts may not be able to guarantee exclusive file locks...
- kreetx 6y agoAbsolutely. What I'm saying is that I personally don't need to know about this. I suspect that OOM's behavior is of similar effect to most developers.
- pjmlp 6y agoIt was more like free beer source code did it.
- throw0101a 6y ago> […] if there's an optimal solution to the OOM problem, I would prefer that all distros use it. Except with the monoculture of systemd how can experiments be done with other approaches? Nowadays it seems like "use systemd or GTFO". > Just like you can mostly expect filesystem behavior to be consistent […] And how many file systems does the Linux support? One can try an approach and see how it works and others can perhaps copy it. How does another approach towards OOM (or anything else in the kitchen sink that systemd handles) get traction when the 800lb/400kg of RH/IBM is bankrolling The One True Way™.
- Nextgrid 6y ago> Except with the monoculture of systemd how can experiments be done with other approaches? Nowadays it seems like "use systemd or GTFO". Is that much different from let's say databases, where "One True Way" was SQL and despite that NoSQL became a thing and is appropriate for some use-cases? > And how many file systems does the Linux support? And yet ext4 appears to be the most widespread though. It's true that there are other options such as XFS, ZFS and BTRFS but in general, ext4 is a safe default that works well enough for most use cases unless you have specific reasons to choose otherwise. Is it that far-fetched to believe that systemd might be the same, and it works "well enough" to be the default and even be bankrolled by some big names? > How does another approach towards OOM [...] get traction Presumably the systemd OOM killer can be disabled and something else put in its place if you so desire, just like you can still build or use a distro without systemd or selectively disabling its "bad" parts such as the journal, etc?