GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok, do you leave your box on 24/7 and if so WHY? I run folding on mine but I'm still noit allowed it on 24/7 - my record uptime is 4 days 9 hours 27 mins - anyone smashing that, I bet there is ;-)
If you don't leave it on 24/7 why not? I'm not allowed but would do to run folding...
I never turn my computer off. Mostly because I am on it so often that turning it off and on would drive me nuts. I have a computer in my house that acts as a router... I think its record uptime was over 90 days... then we had those hurricanes here in Florida. I don't know what it has as an uptime at the moment.
When I lived in the dorms at college my uptime usually went by the semester. I was too busy to play with changing my operating system or anything like that.
Now, my uptime roughly averages to about 20 days (not counting the server... which is never turned off) and that is because I apply kernel patches and stuff. If I was to skip those... it would be much longer.
so far my server runs an uptime record of ~65 day. it would be longer if it weren't for crappy wiring in the house and for my kids finding that pretty green button.
my laptop has a record of about 9 days. the reason it is so short is cause i transport it to and from work. sometimes the card ties up and freezes the system so that even the keyboard stops responding.
My servers (2) I never turn off.. currently after moving to a new apartment, they are at a measily 50+ uptime on both. My desktop I only turn off when I know I'm not going to use it for 8 hours or more... first to save energy and keep my electric bill down and another to save the life of the computer. Turning it off and on too often can kill the overall life.
Its like we have servers at work we're scared when we have to reboot them or power them down, cause some have been running so long, we're afraid the hard drive won't start spinning again if powered off for too long..
And some crap developer asked us to reboot one server the other day cause he said it was really slow, we had a 634 day uptime on it.. it was sad to reboot but we hesitated on the reboot as well..
Originally posted by trickykid
[BIts like we have servers at work we're scared when we have to reboot them or power them down, cause some have been running so long, we're afraid the hard drive won't start spinning again if powered off for too long..
And some crap developer asked us to reboot one server the other day cause he said it was really slow, we had a 634 day uptime on it.. it was sad to reboot but we hesitated on the reboot as well.. [/B]
My longest was 64 days. I reboot after each kernel patch on my file server though (Suse 8.2 with 2.4.20 patched mucho) so I'm curious how you maintain such long uptimes is you update your kernels. Is there a method to update your kernel without a reboot?
Originally posted by Franklin My longest was 64 days. I reboot after each kernel patch on my file server though (Suse 8.2 with 2.4.20 patched mucho) so I'm curious how you maintain such long uptimes is you update your kernels. Is there a method to update your kernel without a reboot?
My own personal record is 235 days.. and to do this means you don't do any kernel updates. These are usually machines of mine that are behind a firewall, with limited access, etc.
But the one machine that did have 235 days was using the 2.4.24 kernel I think.. at the time the only security vulnerabilities that were around were local access only type, so I didn't worry about upgrading since I was the only person with an actual shell account on this machine..
But I'm not the type that runs out and gets a new kernel just cause there is one.. I stay updated and only update if I feel I really need to.
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
I always leave my computer on, but the question which remains is if I leave it on with Linux or with Windows XP. The ONLY reason I use Windows XP right now is to play Counter-Strike:Source, which I play a lot! I also leave it on because I run folding@home for our Linuxquestions.org team!
i boot when a new kernel is being installed by dist-upgrade. but basically itīs 24/7 without any glitches (sarge box). i had to buy a new box a few months ago since my 6-years old motherboad fried. i just did a network install and copied home folder from my 6y-old hard disk. whole switch took only 1 hour that is what i love in linux!
i use it via ssh from my powerbook@home with wlan local network, my wife uses it as a desktop. other times i connect to it from my work with windows&putty. i could never build so reliable system with windows.