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.
You should point cron to the complete path, so use /usr/bin/touch instead of just touch (if SUSE places touch in /usr/bin). Or create a PATH assignment at the crontab file's top ("PATH=/usr/bin" IMHO).
I have SuSE Enterprise 9. I'm not sure how to enable a cron.log. This is what I discovered last night: If I stopped cron and restarted cron, then the crontab works. So I know I'm not going crazy. Anyway, I shouldn't be required to stop and start cron to implement new changes to crontab. This sounds like a problem with cron. The cron rpm release is: cron-3.0.1-920.7
1. If you have paid support, ie from Novell, why are you bothering us, volunteers?
2. Cron looks at the last modified times on the directories that hold the cron files to see if it needs to (re)load modifications you made. Have you checked out those timestamps?
Oh my! This didn't appear to be a support issue. Sorry for bothering you.
It wasn't my point to scare you away from these forums. They're a great place to get help.
My point is simply that paid support implies that you give someone money to fix your problems and to fix them fast. These forums, driven by volunteers, may have a lower response time than that and what would be the point of paying someone for support and then go an ask it to some (free) volunteers? Make the support earn whatever you pay them!