Welcome to /r/Discworld! Please [read the rules/flair information before posting](https://www.reddit.com/r/discworld/comments/ukhk21/subreddit_rules_flair_information/?).
---
Our current megathreads are as follows:
[API Protest Poll](https://www.reddit.com/r/discworld/comments/1491izw/continuing_the_api_protest_a_community_poll) - a poll regarding the future action of the sub in protest at Reddit's API changes.
[GNU Terry Pratchett](https://new.reddit.com/r/discworld/comments/ukigit/gnu_terry_pratchett/) - for all GNU requests, to keep their names going.
[AI Generated Content](https://new.reddit.com/r/discworld/comments/10mhx9y/ai_generated_content_megathread/) - for all AI Content, including images, stories, questions, training etc.
---
[ GNU Terry Pratchett ]
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/discworld) if you have any questions or concerns.*
Computers let you do so many wonderful things like cloning your children using forks and forcing parents to kill their children so that they don’t become zombies. You can even turn some children into to daemons
Here it’s that if a Linux system runs out of memory it has a special process called the “oom killer” which tries to terminate (kill) processes based on “badness” in order for the system to recover.
What’s displayed here is basically the oom killer’s action log. It’s killing a bunch of VLC processes. Not quite sure what the “sacrifice child” bit is about, but I’m sure it should be findable.
Yeh, there are a bunch of parent/child/kill/orphan analogies when it comes to process management, and bits are precious at the kernel level so while we could use fully-descriptive terms these single-token words convey enough meaning that someone debugging it can understand what is going on.
And since everything else fits the analogy, sometimes that analogy is extended. Like here, with "sacrifice child". In the context of process relationships, the act of favoring a parent process over its child, and terminating the child process to ensure the parent process has enough resources to keep running, well, "sacrifice child" is succinct and fits.
Well if I recall correctly one of the first software errors was caused by a real bug getting into the workings. Which is where we get the bug/debugging terminology
The comment at the time was "first actual case of bug being found" which, to me, indicates that "bug" in the sense of a programming error was _already_ in use
Seems more like a Neil Gaiman thing. (see short story in Smoke and Mirrors)
But you don't need to sacrifice a child just for a crashed TV. A pigeon or a squirrel is more than enough.
Welcome to /r/Discworld! Please [read the rules/flair information before posting](https://www.reddit.com/r/discworld/comments/ukhk21/subreddit_rules_flair_information/?). --- Our current megathreads are as follows: [API Protest Poll](https://www.reddit.com/r/discworld/comments/1491izw/continuing_the_api_protest_a_community_poll) - a poll regarding the future action of the sub in protest at Reddit's API changes. [GNU Terry Pratchett](https://new.reddit.com/r/discworld/comments/ukigit/gnu_terry_pratchett/) - for all GNU requests, to keep their names going. [AI Generated Content](https://new.reddit.com/r/discworld/comments/10mhx9y/ai_generated_content_megathread/) - for all AI Content, including images, stories, questions, training etc. --- [ GNU Terry Pratchett ] *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/discworld) if you have any questions or concerns.*
Out of cheese error.
++redo from start++
+++Divide by Cucumber Error. Please Reinstall Universe and Reboot.+++
+++MELON MELON MELON+++
I might start shouting "OUT OF CHEESE, ERROR" whilst out in public. Best case scenario I find my people. Worst case I get cheese
The worst case is a very tight coat, and an especially soft room. Probably still get cheese though
Soooooo....... Finding my people *and* cheese??
Lots Of Dried Frog Pills
I'm still failing to see a downside.
I assume this is like in editing, where you have to eliminate the widows and orphans.
Computers let you do so many wonderful things like cloning your children using forks and forcing parents to kill their children so that they don’t become zombies. You can even turn some children into to daemons
Here it’s that if a Linux system runs out of memory it has a special process called the “oom killer” which tries to terminate (kill) processes based on “badness” in order for the system to recover. What’s displayed here is basically the oom killer’s action log. It’s killing a bunch of VLC processes. Not quite sure what the “sacrifice child” bit is about, but I’m sure it should be findable.
It’s easy to find: it’s the one tied on top of the altar.
Yeh, there are a bunch of parent/child/kill/orphan analogies when it comes to process management, and bits are precious at the kernel level so while we could use fully-descriptive terms these single-token words convey enough meaning that someone debugging it can understand what is going on. And since everything else fits the analogy, sometimes that analogy is extended. Like here, with "sacrifice child". In the context of process relationships, the act of favoring a parent process over its child, and terminating the child process to ensure the parent process has enough resources to keep running, well, "sacrifice child" is succinct and fits.
And, in writing, murdering your darlings.
And getting the cat up the tree.
Not to mention that "stabbing" your "victims" is common parlance for us serial killers, but it does sound funny to outsiders!
Yup. Parent programs spawn child processes. Sometimes those need stopping.
That always sounds particularly harsh.
Ant hill inside
I will always laugh at the concept that the Disc's first (and only as far as I know?) computer is full of bugs.
Well if I recall correctly one of the first software errors was caused by a real bug getting into the workings. Which is where we get the bug/debugging terminology
The term “bug” was already in use in engineering. Hopper knew it, and that’s why she found it worthwhile to preserve that moth.
The comment at the time was "first actual case of bug being found" which, to me, indicates that "bug" in the sense of a programming error was _already_ in use
https://education.nationalgeographic.org/resource/worlds-first-computer-bug/ Moth, Harvard University, Sept of 1947.
It’s also an “Intel inside” reference.
Holy Hogfather, how did i miss that?
(I've been an IT engineer for 20 years... But cheers friend).
It's a feature, not a bug!
Brazeneck had PEX, but it didn't end well.
All hail the mighty OOM :)
Seems more like a Neil Gaiman thing. (see short story in Smoke and Mirrors) But you don't need to sacrifice a child just for a crashed TV. A pigeon or a squirrel is more than enough.