[TriLUG] Computer Getting Slow
john at radiomind.com
Fri Aug 22 12:46:23 EDT 2003
Dan Monjar wrote:
> --On Thursday, August 21, 2003 08:48:54 PM -0400 Jim Ray <jim at neuse.net>
>> if it is quicker to re-load a system with
>> pristine code that to figure out who did what in a past life, then it is
>> more of a benefit to the client to get the job done right for a lower
> Now that is a short-sighted approach... it might be quicker for you, but
> how much time does your client waste getting his now 'pristine' machine
> back to the way he had it configured before you wiped it out? Not only
> does he waste his time this go around, but he'll waste it again in a few
> weeks or month when the problems happens again and you, again, give him
> back a 'pristine' machine. Because you never really did solve the
> problem, did you?
This is silly. We backup the system configurations, and have an image
server that can load an operating system in under 10 minutes. Restoring
the configuration is just a few minutes more. If its a production box,
and I can't afford it being down, I'll take the 15 minute reload over
figuring it out. If it happens again, I'll probably try to get a
snapshot before the re-image, and work offline at trying to figure it out.
Production systems are not learning tools, they are there for the
business and users to get work done. Most if not all bosses don't care
what the fix was as long as the box is back up.
Don't get I would troubleshoot the box for a while, but if I couldn't
find anything obvious, and there was not a good maintanace log for the
computer, its getting re-imaged.
More information about the TriLUG