I can't make this stuff up. Seriously.
Mar. 23rd, 2006 07:32 pm~Two stories for you today!
User (ticket):
Soooo...we just updated and we found a bug!!!11 See, if it's 10:30 AM and make a cron job to execute at 10:31 AM and save it before 10:31 AM, the job is never done! However...if it's 10:30 AM and I create a cron job for 10:32 AM and save it before 10:31 AM, it executes fine! The doc says taht cron scans at the top of every minute. Why isn't this working?! The old one worked.
Me(ticket):
Hi, I've noticed the same behavior on my system. I believe it's just an issue with exactly when you save the job and blah blah blah. I suggest that you set up your cron jobs three to five minutes in advance of the time you'd like them executed. If you'd like, I can continue to look into the issue. Love, Kitty (RHCE)
User(ticket):
Could you look into it for me? I'd really like to know if this is just a bug, or if this is behavor we should expect in the future. I mean, it was REALLY weird when our cron jobs weren't executed!
Me (irc):
Guys, I have a crazy question. *repeats ticket*
Boss (irc):
tell me you're kidding.
Coworkers (irc):
HAHAHAHAAAAAAAAA.
Boss (irc):
If you're not making this up, then you should probally escalate it to an L2, who will shrug and escalate it to the engineers...who will then laugh at it.
L2 (irc):
This is going to be one of those tickets that's open forever isn't it?
Boss (irc):
Yes.
L2s (irc):
NOT IT.
~And...back when I worked at the campus helpdesk, we got a frantic call from a kid that was something like the following:
HELP. BROKE UP WITH GIRLFRIEND AND SHE CHANGED MY CAMPUS ACCOUNT PASSWORD. PLEASE HELP.
~So many things wrong with that. :-D ~
User (ticket):
Soooo...we just updated and we found a bug!!!11 See, if it's 10:30 AM and make a cron job to execute at 10:31 AM and save it before 10:31 AM, the job is never done! However...if it's 10:30 AM and I create a cron job for 10:32 AM and save it before 10:31 AM, it executes fine! The doc says taht cron scans at the top of every minute. Why isn't this working?! The old one worked.
Me(ticket):
Hi, I've noticed the same behavior on my system. I believe it's just an issue with exactly when you save the job and blah blah blah. I suggest that you set up your cron jobs three to five minutes in advance of the time you'd like them executed. If you'd like, I can continue to look into the issue. Love, Kitty (RHCE)
User(ticket):
Could you look into it for me? I'd really like to know if this is just a bug, or if this is behavor we should expect in the future. I mean, it was REALLY weird when our cron jobs weren't executed!
Me (irc):
Guys, I have a crazy question. *repeats ticket*
Boss (irc):
tell me you're kidding.
Coworkers (irc):
HAHAHAHAAAAAAAAA.
Boss (irc):
If you're not making this up, then you should probally escalate it to an L2, who will shrug and escalate it to the engineers...who will then laugh at it.
L2 (irc):
This is going to be one of those tickets that's open forever isn't it?
Boss (irc):
Yes.
L2s (irc):
NOT IT.
~And...back when I worked at the campus helpdesk, we got a frantic call from a kid that was something like the following:
HELP. BROKE UP WITH GIRLFRIEND AND SHE CHANGED MY CAMPUS ACCOUNT PASSWORD. PLEASE HELP.
~So many things wrong with that. :-D ~
no subject
Date: 2006-03-24 01:00 am (UTC)no subject
Date: 2006-03-24 01:07 am (UTC)Patient: It hurts when I do this
Doctor: Don't do that then..
..variety :)
no subject
Date: 2006-03-24 01:08 am (UTC)no subject
Date: 2006-03-24 01:08 am (UTC)no subject
Date: 2006-03-24 01:38 am (UTC)~The basic point of the pointing and laughing is...why schedual something for one minute in the future?! LOTS of somethings at various times, according to the ticket! Why not just wait a minute and execute them? Or--better yet! Hire an intern!
~Or, better yet...plan into the future! Set your stuff up FIVE minutes in advance. If you want to test your cron job...set it for a reasonable time in the future.
~So the point of the point is...people are silly.~
no subject
Date: 2006-03-24 01:40 am (UTC)Your second anecdote reminds me of a call I got when working at Dell. This guy called, and his name was on the account, so I knew the computer technically belonged to him, or I wouldn't have gotten involved...
He had broken up with his girlfriend and she had taken it badly and set a BIOS password on the computer. He'd never seen such a thing before and was desperate to get his graduation thesis off the computer.
Since his name was on the account, I cheerfully walked him through opening the case and moving the jumpers to reset the password. Poor guy. Sometimes you just can't win for trying.
no subject
Date: 2006-03-24 02:19 am (UTC)no subject
Date: 2006-03-24 02:27 am (UTC)Plus it gives you nerd points.
no subject
Date: 2006-03-24 03:05 am (UTC)no subject
Date: 2006-03-24 03:09 am (UTC)also, about the password thing - I've run into that before, only on the other end. I had a roommate who's completely computer-illiterate but when her bf dropped out of school @ the university where she worked, he asked her to get a Unix account so he could use it. Free ISP and all. While they were dating, I didn't say anything, but when they broke up, I logged into her account and changed that password to keep him from mooching off her even more - or maybe even getting her in trouble with the university.
I also have morons putting the wrong email addy in when they sign up for websites so I get all these messages that say "Welcome to our website, Mary!" Since I can't usually find out who they are, I'll log into the websites as them (I can get their password sent to my email address, after all) and change the password.
p.s. I don't think it was an unreasonable expectation that you wouldn't have to explain a cron job here. I know not everyone knows Unix, but more people would here than most places.
no subject
Date: 2006-03-24 03:19 am (UTC)no subject
Date: 2006-03-24 03:44 am (UTC)no subject
Date: 2006-03-24 04:05 am (UTC)~Basically, the crontab is scanned every minute to see if there are any new jobs that it should schedual. Aparently, if you don't define your job and save it atleast 2 mintues in advance, it won't register with it, and so it won't execute.
~I'm not sure that it's really a bug, however...it could just be a slight behavior change.~
no subject
Date: 2006-03-24 04:07 am (UTC)~HAH, that's AWESOME. free stuff for yoooou!
~We used to rearrange the icons on people's desktops when they stayed logged in at a lab computer. :-D
~Well...*shrugs* I didn't know what a cron job really was until I started on at a Linux company (and had to get my RHCE). So....yeah.~
no subject
Date: 2006-03-24 06:50 am (UTC)no subject
Date: 2006-03-24 11:11 am (UTC)~it really didn't strike me as a 'this is odd' claa...more as a 'this is a bug that is impacting us!' e-mail. But then, that could be the user's natural histeria.....~
no subject
Date: 2006-03-24 12:11 pm (UTC)I'm old enough that my first boyfriend broke up with me over ytalk/telnet.
no subject
Date: 2006-03-24 12:27 pm (UTC)And the hysteria because yikes, if cron has something wrong with it, what other previously-thought-bulletproof functions on that system might have all the developmental structural integrity of quicksand?
no subject
Date: 2006-03-24 08:16 pm (UTC)logged in at a lab computer. :-D
I freaked out an old boss of mine at the university when I snuck into her office before she got in for the day and reset her screensaver to the marquee and had it saying "want to go get coffee?"
She came running over and was like "that was amazing! how did you do that?!?" I was tempted to give her a big long explanation involving telepathically sending that message to her computer, but I'm too much of a softie to pull that off.