documentation "lite"

[Denys Vlasenko]

On Wed, Jul 7, 2010 at 9:10 AM,  <beebee at piments.com> wrote:
>> Ok, I admit I was wrong. I confused cron with inetd.
>> cron indeed runs programs using:
>>
>> /bin/sh -c 'commands'
>>
>> and thus "source FILE" thing should work, if you use it like this,
>> for example:
>>
>> 00,15,30,45 * * * * source FILE; command
>>
>> (As an aside, it's better to use ". FILE" since "source FILE"
>> is a bashism).
>>
>>> Where is that syntax documented. I'd refered to vixiecron man pages
>>> installed on my development machine and it says environment variables
>>> "can be set" but does not specify the need to a special syntax or use of
>>> a "crond command" which seems to be what you are doing here.
>>
>> Environment variables can be set like this:
>>
>> 00,15,30,45 * * * * VAR=VAL cmd
>>
>> or this
>>
>> 00,15,30,45 * * * * export VAR=VAL; cmd1; cmd2
>>
>> in other words, using methods you'd use ib shell scripts.
>>
>>> Also what is the time lag on crond rereading the crontabs files ?
>>
>> one hour max. "crontad -e" triggers reread sooner by creating cron.update
>> file.
>>
>>> Std crond reads every time and so no special action is needed after
>>> updating a crontab. This does not seem to be the case with BB crond.
>>
>> Yes, bbox cron does not check every crontab every minute.
>> Only every hour.
>
> Where is this fully documented? The doc on the site is very brief .

What "this" refers to? crontab format? crond reread behavior? something else?

Where do you want this information to be?

Can you propose the text of said documentation?
-- 
vda