Problem with cron

Steven Stern subscribed-lists at sterndata.com
Sat Mar 23 18:56:13 UTC 2013


On 03/23/2013 12:47 PM, Joe Zeff wrote:
> On 03/23/2013 08:58 AM, Steven Stern wrote:
>> On 03/22/2013 03:16 PM, Joe Zeff wrote:
>>> I have my computers registered with the Linux Counter, and my main
>>> desktop machine is supposed to update its status once a week, using a
>>> cron job:
>>>
>>> # added by lico-update.sh version 0.3.14
>>> 58 11 * * 4 /home/joe/bin/lico-update.sh -m
>>>
>>> The permissions on the script are right, and if run manually, it works.
>>>   This worked fine under Fedora 16, but doesn't now that I'm running F
>>> 17.  Does anybody know what's happened, or how to find out?
>>
>> A couple of thoughts:
>> 1.  Does the script have executable permissions?
> 
> Already answered in what you quote.
> 
>> 2.  Is cron working at all? Add "58 11 * * 4 touch /tmp/cron.test" as
>> another cron job. Does the test file date change?
> 
> An interesting possibility.
> 
>> 3.  Just for laughs, check the SELinux logs to see if there's an AVC. It
>> may be that the script that created and installed the file didn't set
>> the selinux permissions correctly.
>>
> 
> I'm not getting any alerts, and if that were the issue, I would.  And,
> if you'd like to examine the script, you can find it here:
> http://linuxcounter.net/script/lico-update.sh

One of those things that can bite you in the butt is that the
environment for /bin/sh might be different than than in /bin/bash,
especially as invoked by cron.

Also, shouldn't the line starting with "scriptversion" be a comment?

-- 
-- Steve


More information about the users mailing list