Quoting Braun Brelin (bbrelin at openapp.biz):
> Would that that were true. Unfortunately we've seen situations where
> older Linux systems become unstable for one reason or another.
In my experience, this would be almost always because it wasn't installed
with journaling filesystems (which wouldn't have been common at the time
of system creation), it wasn't on UPS, and the system got thrashed by
power-cycling.
In other words, that failure mode isn't typically going to happen, any more.
Properly set up background-services-providing systems should normally
run until hardware failure -- modulo security compromise or the need to
reconfigure to accomodate unanticipated changes in the surrounding
environment.
> I recently went to a new customer because his named stopped working
> correctly.
Pray do tell: What about a nameserver "stops working correctly" beyond
the cache getting horked or kernel TCP congestion / filehandle
exhaustion, which of course can be cleared by Ctrl-Alt-Del and waiting
30 seconds?
Which of course one would want covered in the "Admin for Dummies"
binder.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
