Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
I have a cron job that runs everyday at set time--the job executes and runs but will not write to a logfile--0k. The kicker is that when I run the job manually it works and logs just fine. I am grateful for any help at this point.
Hello there and welcome to LQ. Hope you like it here.
the job executes and runs but will not write to a logfile
If it prints to stdout then the report could be in the email (of the crontab user).
If it's not in the email then try appending "2>&1>>/some/logfile" to the crontab line and see if that fixes it.
Else if it doesn't print to stdout, does it have a logfile writing flag?
If it does, does the user you run it as (crontab user) has the permission to write to the logfile?
Else please post what app this is about.
Thanks for the suggestion--unfortunately it did not work. The app in question is Avast antivirus. I know there are ALOT of people that will tell me that AV is not needed or "why bother with AV on Linux" but it is a necessity in this situation.
AntiVirus will most likely be run as root user.
Have you set up mail for root properly? In some cases, for instance, a mail alias is used to send root's e-mails off to a "real" user.
Also, if it works manually, but not from cron, one of my first suspects is usually the environment variables.
Cron jobs use their own environment settings, so please check if the variables you use are properly set.
I have finally figured out the problem. There is a bug when trying to run avastcmd with cron. The people @ avast have sent me the "fix" and I am going to try it today. I will report back with any pertinent information.