Re: cronjob failure newbie question

From: Bill Marcum (bmarcum_at_iglou.com)
Date: 10/14/05

  • Next message: Bill Karwin: "Re: pattern search" 
    Date: Thu, 13 Oct 2005 18:31:01 -0400

    On 13 Oct 2005 14:33:48 -0700, Sashi
      <smalladi@gmail.com> wrote:
    > Hi, I setup a cronjob to run daily:
    >
    > 30 17 * * 0-6 /dev/home/malladis/progs/snapIST/update.sh
    >
    > In the update.sh, I had some binaries which I was executing. The
    > cronjob failed as I didn't mention the full path of the binaries. Is
    > this normal?
    If the binaries are not in /bin or /usr/bin, or whatever is the default
    PATH when a cronjob is running, that is normal.

    (/dev/home? On every system I've seen, /dev only contains device files
    and perhaps the MAKEDEV executable).

    > Also, one of the binaries uses a library file located somewhere in the
    > PATH and the cronjob failed again (after I gave full path names to the
    > executables) complaining that it couldn't find the binary:
    >
    > ld.so.1: /fidev/home/malladis/progs/snapIST/update.cache: fatal:
    > libtibrvcmq.so: open failed: No such file or directory
    > Killed
    >
    >>>From what I know, cron spawns a new shell to run this job. It looks
    > like the shell's path is not getting updated. Am I right? How do I
    > correct this?

    Write a script that sets PATH or sources your .profile, .bashrc or other
    script. 

    -- 
Cinemuck, n.:
	The combination of popcorn, soda, and melted chocolate which
	covers the floors of movie theaters.
		-- Rich Hall, "Sniglets"
  • Next message: Bill Karwin: "Re: pattern search"