[rrd-users] Re: One other quickie :-D

[Anders Ringaby]

In my experience, most cron jobs are not executed as user bin.
Instead, they are executed as root in most cases, or as some
normal "application user" ( who has been added to the system ).

Maybe bin is frequently used for cron jobs on systems that you
are used to, but your advise will not work for Mohammed if his
system is like the ones that I have seen. Furthermore, the
sysadmin or the "application user" decide themselves what cron
jobs to run. It doesn't just happen to be someone ( like bin for
instance ).

But we both agree that this could be a matter of permissions
( see my earlier mail regarding this subject ). Mohammed has
already tried absolute path names, but that did not seem to work.

Another thing that Mohammed can check, is if the cron job is
really activated. He can check this by logging in as the particular
user, and then run the command "crontab -l". If this command lists
the users crontab file on the screen, and if this output shows the
particular job, without any leading "#", then the job is activated.
He may also run the command "mail" ( as that user ) to see if cron
has mailed any messages about the jobs. If there are any cron job
errors, they may appear in the unix mail messages.

Anders Ringaby


On Tue, 26 Jun 2001, Shipley, Rob wrote:

> 
> Have you "su bin" and executed the scripts as bin?(Most cron jobs are not
> executed as user root, they run under bin). Most likely, make sure the
> scripts are executible for bin. ie "chmod +x" as root or chown bin:bin. 
> -----Original Message-----
> From: Mohammed Burney [mailto:rockit at wam.umd.edu]
> Sent: Monday, June 25, 2001 7:20 PM
> To: RRD Tool Users
> Subject: [rrd-users] One other quickie :-D
> 
> 
> 
> Hello all,
> 
> Thanks to those of you that replied to my question. It really helped, heck
> it fixed my problem :-)
> My other problem that I wasn't able to get my perl scripts that update the
> RRD to run thru cron. I tried 2-3 different approaches.
> 
> 1) Tried using the 'use RRDs' method, and invoke the updates as Perl
> functions
> 2) Make a system call to update the RRD `rrdtool update ...`
> 3) use pipe to update the RRD "./perl_script | rrdtool -
> 
> All of these methods work independently, meaning that if I run them thru the
> command line, I have no problems. It is just when I run them thru cron that
> nothing happens. I'm running as root, in Mandrake 7.2 from the / directory.
> I asked around and people told me to try and give absolute path names, which
> I did, and still nothing happened.
> 
> Thanks once again :-)
> Mohammed
> 
> 
> --
> Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
> Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
> Archive     http://www.ee.ethz.ch/~slist/rrd-users
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
> 
> --
> Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
> Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
> Archive     http://www.ee.ethz.ch/~slist/rrd-users
> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
> 


--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi