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.
That won't work either as the file "tester" probably doesn't exist either. And, if /home/tester/ff/python is the path to the python interpreter, then it should work fine the way you are trying to do it. However, you have a path of "tester/home/tester/ff/python". Are you sure your error message isn't:
/bin/sh: tester/home/tester/ff/python: No such file or directory
You don't specify a user in a crontab entry. The cron job will be run by the owner of that particular crontab. If you need to run a cron job as a particular user, create a different crontab file for that user (crontab -e username).
lord-fu & sbabcock23, I think the problem may be that you are trying to edit a non-system crontab entry with a system crontab entry format. Only the system crontab (/etc/crontab) uses the user field. The root crontab doesn't, and neither do any for normal users.
sbabcock23, If you are running "crontab -e" as root to edit the crontab, then there isn't a user field as this is the root user's crontab, not the system crontab. The entire line after the time specifications is treated as the command/options. If you are editing /etc/crontab directly, then you would use a user field. I typically leave this file alone and create per user crontab entris as it makes copying crontab entries from Linux to Solaris and back compatible. If you are running "crontab -e" as the tester user (what I suggest) then you will also not have a user field in the crontab entry.
hey, I got the cron to work except, in my python code I have file = open(filename, 'a') and python is throwing an error:
sys.stdout = open(logfile, 'a')
IOError: [Errno 13] Permission denied: 'log.txt'
but this works if I run it manually but not from the cron job. I added the cron job by using the command crontab -e.