On 07/07/10 01:29, Denys Vlasenko wrote:
> Indeed console output now shows I am getting both the "env DELAY=16 "
> crontab and the original without a delay which is now commented out with
> a #.
This could be a bug. Please describe in more detail.
> It seems it has read in the new line but not dropped the old one that is
> not longer in crontabs.
>
> Is this expected behaviour?
No.
This happened before I realised how long it took crond to reread
crontabs. At one point I had console output Which had two versions being
triggered. When I checked back to the crontabs flie one was commented
out. It is possible it was not commented out when at the time crond
reread the file.
I'll try to reproduce.
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
