One of my co-workers got cute and asked for "root@hpe.com" .... And boy, there's a lot of cron jobs running at HP.
HPE was truly a trip. I paid $2000 to be able to disparage them online and it was worth every penny.
It takes an Act of Congress, a Papal Conclave who produces white smoke on the first vote, Divine Intervention, and Interdiction by a Vice President, all offered in triplicate upon the altar of subpar IT support organizations, to get a ticket closed -with- a resolution in less than a year. If it’s not something they already have a script for it’s almost certainly impossible as far as IT support is concerned.
The company makes billions of dollars a year, employs tens of thousands of people, and they still can’t craft a competent and empowered IT support organization. Even if just for their own developers and technical experts.
I look at it more like a "productivity multiplier", where spending money wisely can make other departments more cost efficient beyond the cost you put into IT. I guess they don't teach that in business school, or everyone is already as productive as they can possibly be. Somehow I doubt it, though.
It was insane to type that, and no one could really work with it. And we had several alias domains.
An IT director actually came to me and said “we can shorten that if you’d like”.
Sure. I ended up with lastname@company. That created a lot of chaos for a few days because my initial username had already been fully propagated. These were the days before niceties like SCIM, so everything was in-house glue, manual work, or obscure third party solutions.
All the code is Apache 2 so I guess if I really cared I could just revive it... and as it turns out, I don't care that much. Other stuff to do.
This is exactly how Epic the Electronic Medical Record company operates, but on new college grads instead of Engineers.
I’ve been out of the work rat race for over 3 years now, but I’ll have to go back within a year… and I’m dreading it.
It’s my most valuable skill set, I just want to throw up when I see what the industry has become and I don’t know how to deal with it.
(My primary care doctor's office was venture-funded at one point and they actually have a great system. But all my specialists are on MyChart and everything there is always a disaster. Doesn't even have a "preferred name" field, so it has to be noted on my records on a case by case basis and it's ... inconsistent.)
There’s something of Bob Hoskins’ heating engineer in what you’ve described.
This company had a rule where the mail was first name + last name initial. So, timc@company.com if you're Tim Cook. Naturally they ended up hiring a customer success person called "Ana Lopes".
She of course noticed on the first day and complained, but IT dragged their feet until some high-profile customer saw "reply to ANAL" in the automated ZenDesk email and send an angry email to the CEO.
So now I'm free to tell people that they fired me with zero days' notice and zero severance. That's just the way they roll.
I find it funny that their nondisparagement policy specifically causes disparagement that otherwise couldn't have occurred.
† They also gave me an explicit reassurance that I shouldn't worry about my health benefits, because those would remain good until the end of the month. I didn't find this particularly reassuring, since it was Halloween.
You're saying that if someone offers me a small amount of money I should accept it, but if someone offers me a large amount of money I should maybe reject it?
That sounds backwards to me.
in that case, rightfully you should not take the money regardless of the amount.
but, if it's a tiny amount of money (tiny enough to indicate that the company probably isn't going to bother coming after you in court) then you can maybe consider taking it anyway and accepting the miniscule risk
whereas receiving a vast sum of money would carry a much larger risk of legal action
bribe?
The QSECOFR (Security Officer) user is effectively root on OS/400.
I would've thought they would run these jobs as some other user, but apparently not.
(Not from "Brazil" the film, but Monty Python-originating regardless.)
on edit: I do remember we had to come back to the course the next day, so it took a day to get it fixed.
I read the last sentence 'And boy, there's a lot of cron jobs running at HP.' in Newman's voice:
From the Seinfeld episode The Diplomat's Club:
"I took over his route. And boy, were there a lot of dogs on that route."
cron jobs reports activity by email to the user (UID) they are running, historically UNIX boxes have the ability to handle mail locally (people would leave messages to each other by connecting to the same server via terminal), so that the root cron activity would land into the root (/root) account mbox file.
When email got interconnected more across servers, generally the service that would dispatch mail to the users account on their home folder on the server started to be able to forward to to others servers, if a domain name was provided. Add to it the ability to fallback to a _default_ domain name for sending email into the organization, and voilà, the root email account for the default domain name receives the entirety of the cron jobs running under root of all the servers running with the default configuration and domain fallback.
In practice, I have never seen a Linux server with an actual SMTP server configured correctly in 20 years, so the worst that usually happens is that cronjobs never actually leave the machine. You used to get a mail notification when you logged in if cron had written something, but that doesn’t happen anymore on recent distros.
In my case, I configured Postfix to redirect all mails looking like (root|admin|postmaster)@server to myemailaddress+(root|admin|postmaster)_server@domain and Postfix ignores what comes after the + in the user part. So I get all the emails but I still know where they come from. It has worked well for quite some years now but I'm not deluding myself, I know that at some time, that will rot too.
This is an important distinction because if you have configured mail forwarding, your cron jobs should be configured to output only on error.. then any emails are actionable.
When I set this sort of thing up, I'd get myself a hostname on an internal subdomain. But that was a truly miserable experience. It was a multi-stage form submission on a server I imagine to be the closest possible relation to an actual potato. It was soul-destroyingly slow. Alternatively, you could just pretend your machine was hpe.com - the hostname was valid, even if the IP was totally wrong, and the SMTP server would accept it.
My guess is that there was a bunch of stuff that pre-dated the HP/HPE split and they took the quick and dirty option whenever the old internal domain name got yanked during the changeover. And if your process runs as root, you get root@hpe.com and hope there's something in the subject/body to identify the specific machine.