Cron scheduling behaviour

[nfo.caesar]

Hi there,

i stumbled over a problem with cron.
I don't know if it's a bug or a known feature
or the other way round.....

The problem is:

see this syslog-entries which show a typical 'crontab -e'-session:

    Feb  7 12:31:46 quepasa crontab[11153]: (service) BEGIN EDIT (service)
    Feb  7 12:31:48 quepasa crontab[11153]: (service) REPLACE (service)
    Feb  7 12:31:48 quepasa crontab[11153]: (service) END EDIT (service)
    Feb  7 12:32:04 quepasa /usr/sbin/cron[10641]: (service) RELOAD
(crontabs/service)

if the user "service" would made have this entry to his/her crontab...

    32 * * * * cd /usr/local/mnogosearch && ./sbin/indexer -a -p 1

.... the first time this command would run is an hour later than probably
expected.

Be aware of this if you "just want to test this new cron entry and set the
schedule to the next minute" like i did when trying to assign
a scheduled job for "service" to run mnoGoSearch's "indexer".


--joko.