On Wednesday 07 July 2010 09:02, [email protected] wrote: > 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.
Can you be more specific? What was in old cromtab? In new crontab? How did you see both entries running - ps? If yes, what exactly it shows? IOW, can I have a _proper_ bug report please? -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
