Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Hello, i have a little Dell server with Debian 5 with samba and a webserver. I would like to know if you suggest to schedule a server reboot or do you think this is not usefult for server stability?
I thought to reboot the server at 2 AM, or better to shutdown it at 0AM and poweron (if I can setup it by its bios) at 7AM.
Personally I would not do this. If you have got some special requirements where in reboot or shutdown is necessary, you could do that but if there is no such requirement, why do it?
Both Dell servers and Debian are robust products and would definitely run without issues on months together.
There have been instances where Linux servers were not rebooted for several months or year or so.
I have several Debian servers (10) running at our office and none of them has a scheduled reboot configured. We also have Windoze servers (45) and they need a regular reboot. In my opinion a scheduled reboot is not necessary on a Linux server if it's administered correctly.
The only reason for doing so would be electrical energy conservation -- think of the penguins -- but even then the thermal cycling may make components fail early and there's a lot of energy invested in creating them. If you're running AC to extract the heat created by used electrical energy then the savings are more significant.
Thanks you all,
i thounght to reboot becausa i came from a windows sistem ... so you can understand my question!
Furthermore, I think that 7 hours per day of poweroff can be good for the components stress and maybe can reduce the hardware failure (-30% of use)... but maybe is a bad idea just because i'm very new of server administration.
Thanks again, i think i will not schedule reboot ...
I would disagree OP that shutdown and reboot would increase the life expectancy of components. It should rather be opposite of what you think.
The more you reboot the machine, more the temperature variations components have to handle. The more the temperature variations, more the wear and tear. That would in turn reduce the life of your hardware.
I did not know that... thanks again.
Do you think that in a good server must be installed something as monit?
This is not a big server and this has nothing so important (file sharing and a management web application).. but i don't know if a process crash can be happend often.
It would depend on the usage. If you have got a good hardware resources and you think your memory would seldom be a problem and no process will die for lack of memory then you can do without it. But it is a personal choice. Monit is just an application. If you think you do not need complex monitoring, you can use some simple to use monitoring like top, ntop and all.
But it is definitely suggested that you do monitoring in some form.
This tends to happen to any SA who has earlier worked on Windows. I have seen server having uptime for more that 3000 days (They were not patched due to some business need) and serving happily ever after.