Subj : Re: Cron
To   : Al
From : Avon
Date : Sun Mar 07 2021 04:20 pm

On 06 Mar 2021 at 07:13p, Al pondered and said...
 
 Al> That's a cron thing. Cron has a very limited environment by default.
 Al> Either use full paths or add the needed environment to scripts being run
 Al> from cron.
 Al> 
 Al> > zip seemed to run but scp did not what is the best way to ensure these
 Al> > programs like htick, scp, etc. run when called by cron?
 Al> 
 Al> Use a full path to scp. On my slackware box it is /usr/bin/scp.
 Al> 
 Al> When I run hpt from cron I start it with /usr/local/bin/hpt. hpt doesn't
 Al> need an environment because it has the full path to zip and unzip in
 Al> it's config.

I think I've managed to get the infopack script to finally run as intended
but ended up adding more stuff to the scripts PATH statement.

That said I think perhaps the way to go would be to explicitly state full
paths to the executable files... what a total phaff :)

Thanks for your help. I'm going to take a break and do some dinner before I
try to tackle the nodelist script

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.