Bob Proulx:
> Jochen Spieker wrote:
>> Bob Proulx:
>>>
>>> Having a literal '~/' in there works for bash. But it doesn't work
>>> for /bin/sh linked to dash for example.
>>
>> Works here:
… snip
> But that doesn't have anything to do with PATH. You didn't test PATH
> containing "~/" in it. You
Bob Proulx wrote:
> Jochen Spieker wrote:
> > Bob Proulx:
> > > Having a literal '~/' in there works for bash. But it doesn't work
> > > for /bin/sh linked to dash for example.
> >
> > Works here:
> >
> > $ exec /bin/dash
> > $ cd /
> > $ pwd
> > /
> > $ cd ~
> > $ pwd
> > /home/jrschulz
>
> Bu
Jochen Spieker wrote:
> Bob Proulx:
> > Having a literal '~/' in there works for bash. But it doesn't work
> > for /bin/sh linked to dash for example.
>
> Works here:
>
> $ exec /bin/dash
> $ cd /
> $ pwd
> /
> $ cd ~
> $ pwd
> /home/jrschulz
But that doesn't have anything to do with PATH. You
Bob Proulx:
> Jochen Spieker wrote:
>>
>> You still can use
>>
>> PATH = "~/bin:/usr/local/bin:/usr/bin:/bin:/usr/games"
>>
>> if the crontab belongs to the user 'rwp'.
>
> Having a literal '~/' in there works for bash. But it doesn't work
> for /bin/sh linked to dash for example.
Works here:
Bob Proulx wrote:
> Jochen Spieker wrote:
> > Bob Proulx:
> > > # The default vixie-cron PATH is "/usr/bin:/bin", overriding the
> > > environment.
> > > PATH = "/home/rwp/bin:/usr/local/bin:/usr/bin:/bin:/usr/games"
> >
> > You still can use
> >
> > PATH = "~/bin:/usr/local/bin:/usr/bin:/bi
Jochen Spieker wrote:
> Bob Proulx:
> > # The default vixie-cron PATH is "/usr/bin:/bin", overriding the
> > environment.
> > PATH = "/home/rwp/bin:/usr/local/bin:/usr/bin:/bin:/usr/games"
>
> You still can use
>
> PATH = "~/bin:/usr/local/bin:/usr/bin:/bin:/usr/games"
>
> if the crontab be
Bob Proulx:
>
> # The default vixie-cron PATH is "/usr/bin:/bin", overriding the
> environment.
> PATH = "/home/rwp/bin:/usr/local/bin:/usr/bin:/bin:/usr/games"
You still can use
PATH = "~/bin:/usr/local/bin:/usr/bin:/bin:/usr/games"
if the crontab belongs to the user 'rwp'.
J.
--
Nothin
Jochen Spieker wrote:
> But beware that you probably need to use /full/path/to/my-script. $PATH
> is probably not what you expect.
Debian uses Vixie Cron which has some nice extensions, such as that
"*/10" you were using. It also allows you to set PATH for all of your
cron commands. I always hav
Darac Marjal a écrit :
On Thu, Dec 01, 2011 at 12:19:06PM +0100, Jochen Spieker wrote:
Nicolas Bercher:
I'd like use set up a crontab rule from 6 am to midnight, and crontab(5)
mentions:
field allowed values
hour 0-23
Then, I tried something like:
*/10 6-0 * * 1-5 my-
On Thu, Dec 01, 2011 at 12:19:06PM +0100, Jochen Spieker wrote:
> Nicolas Bercher:
> >
> > I'd like use set up a crontab rule from 6 am to midnight, and crontab(5)
> > mentions:
> > field allowed values
> > hour 0-23
> >
> > Then, I tried something like:
> > */10 6-0 * *
Nicolas Bercher:
>
> I'd like use set up a crontab rule from 6 am to midnight, and crontab(5)
> mentions:
> field allowed values
> hour 0-23
>
> Then, I tried something like:
> */10 6-0 * * 1-5 my-script
Using this, cron should execute my-script on 06:10, 06:20 … 23:50,
Hi,
I'd like use set up a crontab rule from 6 am to midnight, and crontab(5)
mentions:
field allowed values
hour 0-23
Then, I tried something like:
*/10 6-0 * * 1-5 my-script
Can this be correct or do I face an overlap issue? (I mean since 0 is the
begining of the *nex
12 matches
Mail list logo
