On Thu, Sep 03, 2009 at 11:41:28PM +0200, Mel Flynn wrote: > On Thursday 03 September 2009 22:23:47 stan wrote: > > On Thu, Sep 03, 2009 at 10:10:13PM +0200, Mel Flynn wrote: > > > On Thursday 03 September 2009 21:02:41 stan wrote: > > > > pnoc# cat collect-subtrees > > > > #!/bin/sh > > > > > > > > echo STARTED >> /tmp/stan > > > > which perl >> /tmp/stan > > > > /usr/local/cricket/cricket/collect-subtrees.pl normal >> /tmp/stan > > > > echo Done >> /tmp/stan > > > > > > > > /tmp stan contains: > > > > > > > > pnoc# cat /tmp/stan > > > > STARTED > > > > /usr/bin/perl > > > > Done > > > > STARTED > > > > /usr/bin/perl > > > > Done > > > > > > > > So, cron is invoking the correct command, and perl can be found, but > > > > the original collect_subtrees perl script silently dies. > > > > > > > > I am convinced it's an environemt probkl`lem, I am just uncertain how > > > > to determine what. > > > > > > I'm not anymore. I'm putting 1 cent on a broken /usr/bin/perl symlink > > > (perl upgrade gone bonkers, f.e. done with ro mounted /usr) and another > > > cent on the perl script using system() function, with pathless commands > > > (that is environment). > > Ok, one liner: > su -m cricket env -i HOME=/usr/local/cricket PATH=/bin:/usr/bin \ > /usr/local/cricket/cricket/collect-subtrees.pl normal > > I've downloaded the 1.0.5 version, but can't quickly see where that would go > wrong with this script. touch is in /usr/bin, so that should work. > Any cron messages in /var/mail/cricket?
I am away from work today, and won't be back till Tuesday. I can't access this from home. I will try your test then. The only messages that are getting to /var/log/cron is just the one saying that the task was executed. -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs. _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"