Date: 10 Oct 2002 13:58:03 +1000 From: Duncan Anker <d.anker@au.darkbluesea.com> To: "DaleCo, S.P.---'the " solutions people' <daleco@daleco.biz> Cc: Michael Collette <metrol@metrol.net>, FreeBSD Mailing Lists <freebsd-questions@FreeBSD.ORG> Subject: Re: FTP gone weird Message-ID: <1034222283.19082.8.camel@duncan> In-Reply-To: <034e01c27010$afc55cd0$fa00a8c0@DaleCoportable> References: <200210091438.26928.metrol@metrol.net> <034e01c27010$afc55cd0$fa00a8c0@DaleCoportable>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2002-10-10 at 13:54, DaleCo, S.P.---'the solutions people' wrote: > I seem to remember a post about cron not doing what the user > did, and it was a shell issue. Try your command in sh, csh, etc., > and see if you can get the same error from CLI, if so, then the > shell is the issue. > > Grasping a straw, <snip> > > Both fetch and curl work off the command line. They also don't > produce an > > error when run from cron. Neither one is actually getting the file > though. > > > > What in the heck is it about cron that goofs these ports up?? It's almost certainly something to do with your environment settings - cron is pretty bare. Make sure that you use full path names from within the crontab and that your script explicitly sets any variables it needs. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1034222283.19082.8.camel>