the daughters of Martha, redux

[serinde]

I had a revelation last night: Of the poor sods who are on pager duty, I'm the only one who, if woken up at stupid o'clock for a system problem, can't say "well, I'm coming in late tomorrow then".

Comments

[otherwise-nyc.livejournal.com]

That's ass. Why is that?

[syringavulgaris.livejournal.com]

Cos the rest of the pager crew is on the sysadmin staff, whereas I am in Support--and I'm also the only member of Support who's in from 9-10am. So if I'm late, the phone goes unanswered for the first 45min. or so of the day. Which would be particularly bad on Mondays.

[arkham1010.livejournal.com]

>nelson<
HAHA!
>/nelson

[heliumbreath.livejournal.com]

Look at the bright side: presuming stupid o'clock is anytime after midnight, you can say "Well, I'll be in at my usual time tomorrow, then."

OTOH, it's possible that the person who's supposed to be in bright and early every morning shouldn't be on pager duty, unless they've really thought this through and they want to let pager issues imperil the office opening on time. And yes, I'm in the same boat as the one person in my group on the train, while the others are all a short drive from the (other) office, so if they ever put me on pager I might not be at my desk at 0800 after call-debris settles.

(BTW, I'm really grateful that this guy (http://blackroses.textfiles.com/sex/sex-cars.faq) isn't one of my users...)

[syringavulgaris.livejournal.com]

He's not one of mine, either. Near as I can tell, his account was closed before I was even hired.

...And we actually have a track file on him--it seems that he was as crazy as a very crazy thing. Zoinks.

[nancaurelia.livejournal.com]

ewwwww!

[heliumbreath.livejournal.com]

... and, replying to myself (yeah, I know, that causes blindness) TPTB announced yesterday they want to add me to the oncall rotation. With the Commute To Hell, I'm left with 3 hours 45 minutes personal time per day, and giving any of that up is so not negotiable.

[xlerb.livejournal.com]

Look on the bright side: there's a pretty decent chance that it's an actual problem, and not some random Internet-weather false-alarm that will have gone away by the time you wake up to check it out, thus leaving you to wait for the damn up-page so you can go back to sleep and then get paged again.

...oh, wait. Didn't you say you got paged over sawmill? That increases the suck value somewhat, but it is still an actual problem requiring actual human poking.

(And if I'd remembered about the log-size impact of secondary-MX issues when I had a strange premonition on Saturday evening and discovered that state of affairs, instead of having it dawn on me only when I got into work on Monday to witness the fait accompli, I might even have prevented it. (Of course, there is also one who witnessed the underlying problem, and went poking about in the spools on Sunday, and did not do that thing either.))

[syringavulgaris.livejournal.com]

I am mostly wondering why the person making the initial notification of potential danger didn't move the troubled customer into the holdqueue straight off, since this has HAPPENED BEFORE AND THERE'S STILL A TICKET ABOUT IT ahem. But I guess I'll find out Thurs.