> > I can only support that! - I have an old 486 with 133 MHz at
> > home, working as
> > a gateway for me at home. I had it running for the first time
> > with a Linux
> > kernel version 2.0.30 for about 96 days, when it crashed. -
> > The reason was -
> > oh, no! - Not Linux! It was a broken CPU-fan! - I used this
> > occasion, put in
> > a more silent fan for the power supply, as well as another
> > harddisk and
> > upgraded to 2.0.36. - Since then, I never rebooted the system
> > again. It
> > currently has an uptime of about 165 days and I expect it to
> > run far longer.
> > My only fear is a powerfailure or that that bloody CPU-fan
> > will break again.
> >
> > Can you tell me, what use rebooting is?
>
> new hardware, sometimes (keyword is sometimes not all the
> time) you may need to reboot for changes in inetd configurations
> to take effect.. /etc/hosts file changes, I have had to.. what
> is your system doing?
You don't need to reboot for most of the above.
1. inetd will notice any changes to inetd.conf automaticlly.
2. /etc/host changes will be noticed instantly, ie whenever you
call gethostbyname() or whatever.
We had one linux box that stayed up beyond 400 days, and only went
down a couple of months ago when our building power transformer was
burned up by a water short...
> how do you run fsck? can you unmount the system drive and
> run fsck on it? And not reboot? If that is the case then rather
> than reboot I'd do that once a week ..
>
why would you want to run fsck on a running system? The purpose of
that is to catch errors caused by improper rebooting (such as hitting
the power/reset button rather than a normal shutdown). But yes, you
can umount the partition, fsck it if it makes you feel better, then
remount it without any problem, although I see no reason to do so.
We run to large linux file servers, supporting a couple of hundred
NFS clients, and we have zero file corruption and do not reboot every
week. We don't even reboot every month...
> > At work (where I use Sun workstations) I have three machines
> > (USER-Workstations!
> > Where there are sitting users at the thing, logging in and out
> > and crashing
> > their applications all day long ;) ) - and these three
> > machines have an
> > uptime of far more than 280 days!!!!! (one is over 290 !)
> >
> does Suns filesystems need to be fsck'd?
>
yes... but only if the system reboots ungracefully. just like
linux. No reason to fsck on a machine that is up and running unless
you have disk drive hardware problems, or controller hardware problems.
And then you are going down anyway to replace parts (unless you use hot-
swap drives).
> > Can anybody please show me *any* NT-User-WS with such uptime?
> >
>
> okay now you are dreaming...
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
> To Unsubscribe: send "unsubscribe linux-smp" to majordomo@vger.rutgers.edu
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/