double *grrrr*
I think LJ ate my post again.
Add this to the list of annoyances for today. :(
I got in to work this morning to find that may machine was rebooted. This is a bitch, not only b/c I usually have a million things open, but also b/c I left something running that I wanted to check the output of this morning. That'll teach me.
The beauty of it is that the other machine in my cube did not reboot. Curious given the fact that my primary machine is on a UPS (a crappy UPS to be sure, but a UPS all the same) and the other machine is not. I come to find out that no one else's machine's had spontaneously rebooted, so power loss was not to blame.
This is annoying.
Later in the morning I get a clue about what probably happened. There was a call on a cell phone that I no longer use last night from a caller who did not identify herself saying that my machine was beeping and she was going to leave work. I'm guessing this is the woman in the next cube. My further guess is that she powered my machine off b/c the script I left running had errored out somehow. Nice work. Now I don't know if or how it errored, so I get to run the multiple hour bitch again today. Joy of Joys. Not to mention the fact that by killing the machine she killed the damn process as well.
And the smart readers have already figured out that it will not finish b4 I leave work today which means what class?? Yes, it will beep again at some point tonight and some kind helpful soul will again do me the favor of stopping the beeping noise. Thanks ever so much, you've been too kind, *really*.
No note on my desk from the helpful soul either. That would have been the polite thing to do don't you think?
As I am typing this my cube neighbor has arrived at work. She has said nothing to me about the beeping. Another coworker came over to find out if the script ran and I explained to him why I did not know the answer to the question. She has still said nothing. Perhaps it was not her after all. Hmm.... I will have to listen to this cell message and figure out who called last night.
Add this to the list of annoyances for today. :(
I got in to work this morning to find that may machine was rebooted. This is a bitch, not only b/c I usually have a million things open, but also b/c I left something running that I wanted to check the output of this morning. That'll teach me.
The beauty of it is that the other machine in my cube did not reboot. Curious given the fact that my primary machine is on a UPS (a crappy UPS to be sure, but a UPS all the same) and the other machine is not. I come to find out that no one else's machine's had spontaneously rebooted, so power loss was not to blame.
This is annoying.
Later in the morning I get a clue about what probably happened. There was a call on a cell phone that I no longer use last night from a caller who did not identify herself saying that my machine was beeping and she was going to leave work. I'm guessing this is the woman in the next cube. My further guess is that she powered my machine off b/c the script I left running had errored out somehow. Nice work. Now I don't know if or how it errored, so I get to run the multiple hour bitch again today. Joy of Joys. Not to mention the fact that by killing the machine she killed the damn process as well.
And the smart readers have already figured out that it will not finish b4 I leave work today which means what class?? Yes, it will beep again at some point tonight and some kind helpful soul will again do me the favor of stopping the beeping noise. Thanks ever so much, you've been too kind, *really*.
No note on my desk from the helpful soul either. That would have been the polite thing to do don't you think?
As I am typing this my cube neighbor has arrived at work. She has said nothing to me about the beeping. Another coworker came over to find out if the script ran and I explained to him why I did not know the answer to the question. She has still said nothing. Perhaps it was not her after all. Hmm.... I will have to listen to this cell message and figure out who called last night.