Sounds like a child process
IT boss left root session open for bring-your-kid-to-work day
WHO, ME? Comedian W.C. Fields is credited with the aphorism "Never work with children or animals," which The Register mentions because half of it has some relevance to this week's edition of "Who, Me?" – the reader-contributed column chronicling the ups and downs of working in tech. This week, meet a reader we'll Regomize as " …
COMMENTS
-
-
-
-
-
-
Wednesday 5th August 2026 01:55 GMT Albert Coates
Re: child process
Thanks, I was referring to down-voters in general - their antics are generally hilarious, except for the carefully considered DVs for our resident "wine and steak" aficionado. PS ratio now 69:1. My subsequent comment garnered 4.5:1, how the haters do multiply. Would any down-voter to care to elucidate the reasons for their negative reactions? Nope, didn't think so.
-
Wednesday 5th August 2026 19:44 GMT doublelayer
Re: child process
I wasn't the original one you complained about or one that contributed to the second ratio you're complaining about, but I have two guesses about why the second one got some. One rule is that complaints about downvotes will get more downvotes from people who dislike those complaints on principle.
The other is that your posts aren't that convincing. You claim that the voters are unable to handle a phrase you only used in one post, so your claim can apply to a maximum of one voter. Some people may think that's an unfair assumption and a useless complaint with so small a target. Now, you're claiming you were speaking in general even though your original comment is incompatible with that. I think I've analyzed this as far as I can.
-
-
-
-
-
-
-
-
-
-
Thursday 6th August 2026 03:06 GMT Eric 9001
Re: Amateur
Reviewing GNU fileutils 3.13 from <1996 (which goes back to 1985), it did not have the --no-preserve-root option, neither does 3.16 (<1997), nor 4.1 (<2001), nor coreutils 5.0 (<2003).
As per ChangeLog of GNU coreutils 5.2.0, --preserve-root and --no-preserve-root were added to GNU coreutils on the 2003-11-09 (presumably added to avoid problems with poorly written scripts that do; `rm -rf /$DIR`).
So no, it wasn't available for GNU rm back in the 90's, nor in other proprietary rm implementations.
But you can still do; `rm -rf /*`, just fine, which the worse bash script writers (like Valve), cause with beauty similar to; `sudo rm -rf /$VAR*` (empty $VAR is equivalent to '' and /''* resolves to /*).
Try it; `echo rm -rf /$VAR*`
-
-
-
-
Monday 3rd August 2026 09:15 GMT Bebu sa Ware
Even back then we locked our serial terminals
AIX as far back as v4 did have a version of the lock command
lock -2000 would lock the (non X11) screen for more than a day [2000 minutes (33h 20')] and xlock for an X11 display.
In practice I think I used the screen command with serial terminals which supported locking although I don't recall that many Unix versions shipped with screen.
I guess much of the internet was built with 24x80 hardware terminals which is another cue for a four Yorkshiremen sketch. (We had a papertape punch for our display, 7 toggle switches for input and edlin…)
These days our zillionaire tech bros masters having "bring your kid to work day" would be expecting your kid "to work" but to be fair I am sure they would provide the empty Cola bottles.
-
-
-
Monday 3rd August 2026 11:31 GMT skwdenyer
Re: Groups!
I think the term “sanely designed” is the key thing here.
Back in the day, we used to have Operators whose job it was to run jobs, etc. Since jobs were only run by these hallowed high priests, they had little scrutiny or oversight, and many argued they *were* the safeguards..:
-
-
Monday 3rd August 2026 12:44 GMT KittenHuffer
Re: Groups!
These days I would argue that, cos the company processes where I w**k proliferate far more and far faster than it would be possible for my cow-orkers to fsck up!
I'm sure that there is someone employed by the company to 'do' company processes, and they have to be seen to be doing something ..... so every three months we get given a bunch of additional processes we have to conform to!
-
Monday 3rd August 2026 13:45 GMT that one in the corner
Re: Groups!
Oh, there is definitely someone paid to "do" company processes.
Ours used to draw lots of lovely process diagrams, neatly drawn out in black and white, no fancy schmancy excess graphics from marketing, just lots of thin line from one box to another.
All carefully exported to the company intraweb as JPEG, so everything had that "am I wearing the right glasses?" blur. PNG? Never heard of it. SVG? Oh, la-dee-dah Mr Dev wants SVG!
-
-
-
Saturday 8th August 2026 14:28 GMT Scene it all
Re: Groups!
I was a "system programmer" back in those days, which meant I was responsible for installing software updates from IBM. Thus I was told the passcode to unlock the door into the hallowed raised-floor room. One day, while attempting to make a backup copy of the main "procedure library" I accidentally got the cards in reverse order and copied an empty disk pack (remember those?) on top of the active library. I had to go to the tape library room (remember those?), get out the last backup tape, and restore the procedures disk. Without the procedures file, all operations grind to a halt in an IBM shop of those days so the actual "operators" stood around glaring at me as I did this.
So even the hallowed priests can mess up.
-
-
Monday 3rd August 2026 11:43 GMT Androgynous Cupboard
Re: Groups!
My first job was maintaining a program in tens or hundreds of thousands of lines of C which had been auto-converted from BASIC. Loads of "if (b_streq(a, "") == true" to check if the string was zero-length, the vast majority of variables were global and, oh yes: liberal use of "goto"
Frankly keeping the BASIC would have been a better option.
-
Monday 3rd August 2026 13:52 GMT Anonymous Coward
BASIC to C conversion
This couldn't have been the converter I wrote ~40 years ago. It was such a traumatising experience I gave up coding forever.
The guts of the generated C was an enormous switch{} statement where the labels corresponded to the line numbers of the BASIC code. This vile hack was partly inspired by Duff's device:https://en.wikipedia.org/wiki/Duff%27s_device.
If it had been submitted, the code would almost certainly have won one of the earliest Obfuscated C contests.
-
-
Monday 3rd August 2026 17:06 GMT EricM
Re: Groups!
Why, for an self-confident admin, you'd need non-root users at all? /s
Honestly, I remember *nix systems in the 90s even in larger companies, that only had a root user (plus of course the usual stuff: daemon, bin, sys, lp, etc.). So it was not advisable to log on and do anything before the caffeine from the second coffee hit your bloodstream...
In smaller companies this might have been the case much longer.
-
-
Monday 3rd August 2026 13:17 GMT Anonymous Coward
The other half of the kids and animals quote.
We had a data entry temp (the sales manager's wife) in the office copying data from about 5000 file cards into a contact management system back in the early 90s. She was alllowed to bring her dog into the office because it needed to be medicated during the day. It was extremely well behaved, and most of the time just slept under the desk next to her.
At one point when she left the office to visit the ladies room, the dog for whatever reason decided to climb onto her chair and then onto the desk where he managed to knock 2 stacks of file cards onto the floor. One stack had been entered already, the other hadn't. About 500 mixed up cards.
Having to check whether a card had already been entered into the system before she tried entering it again (the system didn't check if a contact already existed until she went to save at the end of entry) added about 4 hours to her processing that batch of cards. We did instigate a change after that, we gave her a pen to tick each card after she had processed it, not sure why we didn't do that from the start.
-
Monday 3rd August 2026 17:44 GMT Anonymous Coward
Sources of Chaos
It could have as easily been a coworker dropping a stack of files, loaded 3-ring binders, or books onto the desk hard enough to shake the desk and mix the cards.
Or it could have been an IT staffer dropping off a new/refurbished desktop PC, or a new/refurbished laser printer.
-
Thursday 6th August 2026 10:48 GMT JulieM
Something similar happened to me at an Open Mic night at a local pub. I had taken my dog (a German Shepherd cross) with me. She was sleeping under my table, so I nipped to the loo. While I was away, she woke up, noticed I was not there and went to look for me. She jumped up onto the stage and knocked over a music stand, sending pages of sheet music into the airstream of a large fan; a guitar; and some lights. Then as I returned to the scene, blissfully unaware of the carnage that had been unfolding in my absence , she caught my scent, ran towards me, and proceeded to greet me as though I had just returned from a voyage around the world .....
-
-
Monday 3rd August 2026 13:33 GMT that one in the corner
Was she named "Molly"?
Never let a child named "Molly" near tech without the appropriate precautions.
-
Monday 3rd August 2026 13:58 GMT Ian Johnston
Many years ago I entered "shutdown" as a command on the Oxford University Engineering Department VAX 11/780 and to my surprise it did exactly what it said on the tin, although I was only an unprivileged student user.
The system manager was a little vexed, but on the whole grateful that I had found a hole in the system, which he assured me he would fix at once.
Two days later friends in another research group asked if it was true that I had caused the outage and if so how I had done it. Yes, I said, and like this, but it won't do anything this time because the problem has been fixed.
Reader, it had not been fixed. The system manager was rather more vexed and less grateful the second time.
-
Monday 3rd August 2026 16:27 GMT CorwinX
It's a rare individual...
... who can be both a good manager and a techie at the same time.
In my long career I never accepted a promotion above team/project leader.
I don't have the personality to deal with people problems. My approach tends to be more along the lines of Mr Travaglia's BOFH ;-)
-
Monday 3rd August 2026 19:11 GMT Antron Argaiv
Re: It's a rare individual...
Made it to Senior Engineer (sometimes Principal and once, Chief, but I was neither) and that's where I wanted to stay. I really, really like designing things, solving technical problems and building sh*t. I have no interest whatsoever in getting roughly the same amount of money to act as an interface between upper manglement and the people who actually do something productive (or don't).
-
Friday 7th August 2026 09:24 GMT Bob Royal
Re: It's a rare individual...
I was made the company's youngest ever Senior Engineer, in the 70's.
All thanks to Ted Heaths stupid socialistic Price & Incomes policy.
It followed that I became youngest Principle on the same basis.
The only time I was made responsible for an underling, things didn't go well.
The chap who was given the role instead of me, built an empire out of it.
My boss who always kept me, despite other manglement, was a manager, not a mangler.
-
-
Monday 3rd August 2026 21:33 GMT Giles C
Re: It's a rare individual...
I’m much the same zero interest in management, I am a techie and reasonably at it.
I usually end up being a lead technical engineer on network projects (not a pm as that isn’t my forte).
But my approach to management is
If you don’t know who to do it you can ask me I will help
If you don’t know who to do it and you break it you are on your own, as occurred in this conversation from just before I left a company
Caller: we have a problem (we…… at this point I am 100 miles from the main office having just been working overnight)
Me: what has gone wrong
Caller: I turned spanning tree off on a port on the core switch and the site seems to have stopped working
Me:Why on earth did you do that?
Callee: Someone suggested it
Me:Well the network has gone into a loop so you need to do three things
1. Go and tell management
2. Shutdown that core if the console has locked then pull the power (this is a Cisco 7010 chassis running about 10 fex extenders
3. Wait 5 minutes check everything is running and then power the core back up it will take about 20 minutes to boot.
Caller: do I have to tell management?
Me: well if you don’t they will realise quickly and then come demanding to know what is going on, this way you may get away with just being told you are an idiot.r
I still don’t understand why turning spanning tree off on a production interface was ever a good idea and without any change documentation…..r
-
-
-
-
-
-
Thursday 6th August 2026 08:42 GMT CrazyOldCatMan
Re: It's a rare individual...
reciprocate with a token of your gratitude
Ahh.. token ring. Surprisingly quick for a headline 4mbps data rate, quite physically robust and, nearly, impossible to break when looked after by someone competent..
Or me. Although I did manage to kill it (temporarily) on my first job as a techie. We had a per-floor setup - each area had its own ring, all joined by a central ring that just acted as a bridge between the zones.
I, being a keen young techie, got asked to repatch one of the local connections as the office had been moved around and some of the connections needed checking and moving. Instead I managed to repatch the central ring.
Walking out of the network room to a whole floor of machines clicking away [1] and the look of fury on my boss's face was not a nice experience. I hastily went back and put everything back where it should be (we, even in those long ago days, had proper cable management so I just had to look at the patching plan I *should* have looked at before doing anything..).
My boss said something along the lines of "every techie is entitled to one major screw up. You've just had yours. Don't do it again". Being Glaswegian it was in a little more.. detail about my shortcomings.
The incident got recorded as "equipment failure".
[1] When a token-ring card doesn't see a token for an amount of time it starts giving out a clicking noise. One machine doing it usually means the user has kicked the cable for their machine and knocked it loose.
-
-
-
-
-
-
-
-
Monday 3rd August 2026 18:17 GMT Gary Stewart
For old timers like me
Export TMOUT in .bashrc (or use systemd equivalent?) with a value in seconds.
I have it set to 15 minutes in .bashrc and have written a BASH script that allows me to set TMOUT to between 5 minutes and 60 minutes (command line parameter is in minutes), disable it with 0, or display the current value of TMOUT in minutes.
-
Thursday 6th August 2026 03:17 GMT Eric 9001
Re: For old timers like me
That exits bash, which may not be wanted if you would like to see previous backlog later.
xscreensaver can lock the whole xorg session in 15 minutes (programs like xfce4-screensaver also work slightly less well at locking - a cat may find a key sequence that crashes it and thus unlocks), keeping all shell state in place until you unlock with the password.
systemd-shelld soon now?
-
-
-
-
Thursday 6th August 2026 03:28 GMT Eric 9001
Re: The owner did a
Might be a different flight I'm thinking of, but it was actually 2 kids in the pilot and copilot seats - a girl and a boy and both were encouraged them to play with the control sticks.
The way the autopilot worked is that minor to moderate inputs were ignored, but big inputs disabled the copilot and were followed - the boy had the strength to apply a big input and applied one.
Then the pilots failed to recover from the upset despite all the height available and then stalled and crashed.
The plane wouldn't have crashed if either pilot had remained in the seat and allowed one to play at time, or had applied correct inputs once either managed to get back into the seat.
-
-
Monday 3rd August 2026 21:37 GMT Anonymous Coward
Happened to me
I was working in medium-sized ISP. The gateway was in one of the windows in a tmux session, I was leaving for the day, late afternoon. I typed poweroff to turn off MY machine. Incorrectly typed in the logged in gateway handling all machines and VLAN traffic.
Stayed 2 hours more fixing stuff :-(
AC bcz I still blush years later
-
-
-
Tuesday 4th August 2026 05:29 GMT Giles C
Re: Happened to me
As long as the colour can be distinguished by said colour blind person (me), colour blindness encompasses a range, for example green and orange are the same (yes grass is orange normally) traffic lights are orange, red, white etc,
There is a reason I only wear one colour of socks, or always wear a white shirt, or want labels of coloured items….
-
-
-
-
Tuesday 4th August 2026 11:11 GMT FeRDNYC
Security through hopes & prayers...
A friend used to have a combined live/work space for his photography business, which meant he'd often have visitors hanging around the studio at all hours and in all states of self-restraint/trustworthiness. Since this was also in the pre-smartphone era of 3G mobile communications, it wasn't yet the case that everyone had an always-ready device in their pocket for accessing their online presence (and even if they did, said access was slow enough to be a deterrent), so whenever people happened upon a computer with a fast broadband link it was often seen as an opportunity to "check my email" & so on.
So, the incentive was already in place for unauthorized persons to access the computers scattered around the space. Not that they'd have malicious intent, by any means, but there was still the possibility of significant accidental harm. See, the friend in question had a stereotypical artist's approach to content management & data security:
PCs had a single account with Administrator access, which was always logged in. (Probably auto-logged-in, except in the latest few years of the setup.)
Project files for a given Client N were invariably (a) on the computer desktop, (b) in a folder named "New Folder (##)" (nearly always a 2-digit number, because there were that many), and (c) open-and-unsaved in whatever application was being used to work on them.
Every application that had ever be opened on the computer since its last restart was still open, and almost certainly had unsaved files. Very frequently, unsaved newly created files, so you couldn't even safely exit the application without assigning a filename and directory location to a bunch of "Untitled Document N"s — which nobody but their creator had enough information to actually do.
You almost couldn't avoid messing something up — even I, who had set up and adminned all of the systems there, couldn't avoid stepping on land mines, because it wasn't a question of technical knowledge. To safely "jump in" on a machine that had in-progress work active on it, you had to know the intent for a lot of things that gave no indication as to their intent, because that information existed nowhere except inside the mind of the machine's owner. (And honestly, i often questioned even that.)
Suffice it to say, it was not an environment where you wanted other people messing around in the session, no matter how innocently.
Eventually, I picked up on all this, especially after being around long enough to start finding predictable patterns in the goings-on. On the eve of one such occasion, at the point where "work time" had been suspended and people were arriving to the space for an evening social gathering — always my cue to depart — I very pointedly and conspicuously told him, "I'm done on that machine, so you can go ahead and log out." The response I got was, "It's fine, everything is exactly the way I want it." Okey-doke. I did my part. Off I went.
The events that followed I only learned of days later, when next I arrived to the space. In a scene ripped straight from the pages of Predictable Events Quarterly, what had happened was:
1. The chosen approach to securing the computer "exactly the way [he wanted] it", rather than logging off, was to switch off the display. And nothing else.
2. At some point, some visitor that evening decided to go looking for a computer where they could "check their email".
3. Unfathomably (except, totally not in the slightest), said visitor spontaneously earned a degree in IT management, and worked out how to switch a screen back on. They were thus undeterred by that impenetrable barrier to their accessing the machine.
4. In bumbling around attempting to reach a web browser, they closed some application (which was no doubt running fullscreen and getting in the way of any attempts to access other software), accidentally destroying several hours' worth of unsaved work.
...And I had to pretend to be shocked and appalled by this completely unexpected occurrence, when all I really wanted to do was spray-paint "I F---ING TOLD YOU SO, IDIOT" on a frying pan and repeatedly smash it into his thick skull.
-
Wednesday 5th August 2026 08:44 GMT Stuart Castle
Back in the early 2000s, when a lot of people didn't have fast access to the internet, my then employer came up with the bright idea of inviting a load of school kids for special training sessions, as we had a good internet connection.
So, myself and my colleague spent a couple of days teaching these kids how to browse the web, how to search. That sort of thing. Well, that was the idea.
Once they discovered Google, we spent our entire time stopping them searching for porn, usually nude pictures of Britney Spears.
-
Wednesday 5th August 2026 09:55 GMT ChrisBedford
This is why as an IT support drone I am unimpressed when (usually older) people tell me their kids / grandchildren "are very good with computers". I keep trying to explain to them that confidence does not equal competence but sadly when faced with such a wildly different different way of doing things from the way they did it at that age, "blasé" impresses the hell out of them. I always wonder if they would be as blown away by the same kid, with the same (i.e. zero) skills got behind the wheel of a Ferrari and just put their foot down, but you might as well talk to a brick wall...