![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
...#1412 in a series.
After the file server migration from hell, which ended at 4 AM for yours truly, some of the lab workstations needed to be rebooted. Apparently, after the migration some of the students needed to use the labs so badly that when they were giving a faculty member a rundown of problems they were having, they came up with this gem:
> "Solvable" Problem: Sun systems freeze when logging on.
> Description: When you attempt to log on to a system in [lab rooms], it freezes on the login window.
> Workaround: Reboot the system. It probably needs to know about the directory structure.
> If you've already logged on, pull the plug; if you haven't yet, hit the power button first and
> turn it back on after it shuts down.
Peeve the first: Well, now we have a pretty good idea of why we've been seeing steady, but sporadic, disk failures and corruption on the Sun workstations in the lab rooms, don't we?
Peeve the second: There's two workstations that need to be reinstalled due to corruption problems, one of which may have hardware problems.
Peeve the third: If we catch them at it, we most likely won't be able to disable their accounts.
Peeve the fourth: They're also most likey the ones that leave empty food containers in the lab.
Peeve the fifth: You're electrical engineers, for Chrissake! What do you geniuses think will happen to the workstations when you start yanking the power cord out, and then plugging it back in? Bonus points if your reply includes the phrase "heads crashing onto disk platters".
BoneUs Peeve: When I got in this morning, and went down to the lab to reboot the workstations, three of them were in use, screens unlocked, by the students, who were nowhere to be found and had most likely gone home last night and left stuff running. Hope that some student doesn't come along and want to use that workstation, guys.
Of course, I'm the one that was in the lab, seeing what machines were in use, and rebooting everything *but* those workstations.
After the file server migration from hell, which ended at 4 AM for yours truly, some of the lab workstations needed to be rebooted. Apparently, after the migration some of the students needed to use the labs so badly that when they were giving a faculty member a rundown of problems they were having, they came up with this gem:
> "Solvable" Problem: Sun systems freeze when logging on.
> Description: When you attempt to log on to a system in [lab rooms], it freezes on the login window.
> Workaround: Reboot the system. It probably needs to know about the directory structure.
> If you've already logged on, pull the plug; if you haven't yet, hit the power button first and
> turn it back on after it shuts down.
Peeve the first: Well, now we have a pretty good idea of why we've been seeing steady, but sporadic, disk failures and corruption on the Sun workstations in the lab rooms, don't we?
Peeve the second: There's two workstations that need to be reinstalled due to corruption problems, one of which may have hardware problems.
Peeve the third: If we catch them at it, we most likely won't be able to disable their accounts.
Peeve the fourth: They're also most likey the ones that leave empty food containers in the lab.
Peeve the fifth: You're electrical engineers, for Chrissake! What do you geniuses think will happen to the workstations when you start yanking the power cord out, and then plugging it back in? Bonus points if your reply includes the phrase "heads crashing onto disk platters".
BoneUs Peeve: When I got in this morning, and went down to the lab to reboot the workstations, three of them were in use, screens unlocked, by the students, who were nowhere to be found and had most likely gone home last night and left stuff running. Hope that some student doesn't come along and want to use that workstation, guys.
Of course, I'm the one that was in the lab, seeing what machines were in use, and rebooting everything *but* those workstations.
