Event JSON
{
"id": "77bb74c0717ec9596d3fe9c94c7bf2893d75c2af4e9d700211d1ad3a6c3370f4",
"pubkey": "7d23b2dbb4b274388ff81c6db82fb0702cacb80de314d62e4be362189c6f6998",
"created_at": 1737435994,
"kind": 1,
"tags": [
[
"p",
"60ead0028c1044fb77ac647f88bca796d22185ab978ade8839d9160757b3825e",
"wss://relay.mostr.pub"
],
[
"p",
"4fbf72f4f23853886f17d785dae040957f149b101524edd02f8d1f73b46d604f",
"wss://relay.mostr.pub"
],
[
"e",
"c9e7c26f41610530641235b8b2f408fb130e5aae26bdab9fa5e43fe915288d40",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"linux"
],
[
"proxy",
"https://fe.disroot.org/objects/05d8db71-aa2e-41df-a5f8-8816880e3a2e",
"activitypub"
]
],
"content": "\n\nIn the history of time has the #Linux OOM killer ever picked a sensible process? 8Gb Rust Rover process sitting right there, but nope the 6.8Mb user dbus-broker looks like a better target, lets kill that and end my entire session. \n\nnostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqvr4dqq5vzpz0kaavv3lc3098jmfzrpdtj79dazpemytqw4ansf0qkv5f2h I know nothing about memory tuning on Linux, but is there really no way to configure the OOM killer algorithm to just choose the process with the largest footprint?",
"sig": "e49cb46e2096d5687001a380b9fc7041062a0d3b645dbf43b13636b6190f0e1e99fb0e92c38f16d74bca95b51a06ec99751559e8521da0a531775e993b222276"
}
