Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Um, not to be offensive, but why in the world would you want to automatically reboot periodically? Is there a specific problem you are trying to solve? If so, please post it because I'm pretty sure there is a better way to deal with it than a reboot.
Besides Hangdog's comment you have to give the full path to the command you want to execute. That's true for all crontab entries, or you can set crontab's own PATH variable at the top of your crontab file. So try "/sbin/shutdown" instead of "shutdown" if you have a good reason to restart it the way you want.
thanks for teh reply
but i acuatly tried that also
for example " 5 0 * * * /sbin/shutdown now -r "
& " 5 * * * * /sbin/shutdown now -r "
then i wrote a file where i mentioned this command shutdown now -r, and then made it executale by "CHMOD file 777"
the file when run executes the job perfectly
I think the better question still remains what Hangdog42 asked: *Why* is a periodic reboot being considered? Linux can run for months without needing to reboot, and unlike Windows which can become unstable over time, there shouldn't be any regular need to schedule a reboot. Besides, it's dangerous - to use just one simple example, if you are running a database and one of your users submits a process that will generate a large series of transactions (for example, running a payroll cycle for a few hundred employees), having the machine reboot in the middle of things is going to create a mess. What is the basis for wanting to schedule a reboot?