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.
>
>
: "Michael Collette" <[EMAIL PROTECTED]>
To: "FreeBSD Mailing Lists" <[EMAIL PROTECTED]>
Sent: Wednesday, October 09, 2002 4:38 PM
Subject: Re: FTP gone weird
> On the recommondation of an off list response I attempted using
some other
> tools instead of "ftp
On the recommondation of an off list response I attempted using some other
tools instead of "ftp". Tried fetch, wget, and even curl. wget didn't like
the port forwarding, cron or not.
Both fetch and curl work off the command line. They also don't produce an
error when run from cron. Neithe
Having a heck of a time with what I thought would be a pretty simple cron job
of pulling down a web log via FTP. In the process, I've run into a wall of
port problems.
The Scenario:
I'm running an ssh session looped back to itself so as to configure a tunneled
port forward from localhost:2121
