On Sun, May 06, 2012 at 11:24:44AM +, Camaleón wrote:
> On Sat, 05 May 2012 18:26:30 -0400, Tony Baldwin wrote:
>
> > I've got a little cron job,
> > just trying to fire off a script (see http://tonyb.us/mattbot ) and it's
> > not firing.
> >
> > I have other jobs on the same crontab that do.
On Sun, May 06, 2012 at 02:07:08AM +0300, Adrian Fita wrote:
> On 06/05/12 01:26, Tony Baldwin wrote:
> > I've got a little cron job,
> > just trying to fire off a script (see http://tonyb.us/mattbot )
> > and it's not firing.
>
> [...]
>
> > Probably something really obvious I'm overlooking, bu
=?iso-8859-1?q?Camale=F3n?= writes:
> Here is a good collection of the common reasons why a cron job does not
> engage:
>
> http://askubuntu.com/questions/23009/reasons-why-crontab-does-not-work
One thing you can do is to set an "at" job to run your
script once. Go to the directory you wa
On Sat, 05 May 2012 18:26:30 -0400, Tony Baldwin wrote:
> I've got a little cron job,
> just trying to fire off a script (see http://tonyb.us/mattbot ) and it's
> not firing.
>
> I have other jobs on the same crontab that do. When I run the script
> manually, it runs.
(...)
Here is a good colle
On Sat, May 5, 2012 at 6:26 PM, Tony Baldwin wrote:
> I've got a little cron job,
> just trying to fire off a script (see http://tonyb.us/mattbot )
> and it's not firing.
>
> I have other jobs on the same crontab that do.
> When I run the script manually, it runs.
[...]
> Probably something real
On 06/05/12 01:26, Tony Baldwin wrote:
> I've got a little cron job,
> just trying to fire off a script (see http://tonyb.us/mattbot )
> and it's not firing.
[...]
> Probably something really obvious I'm overlooking, but the more I look,
> the less I see why there's a problem.
>
> any and all a
6 matches
Mail list logo
