From: Jamie C. <jca...@we...> - 2003-09-25 06:08:28
|
Martin Mewes wrote: > Hi Jamie, > > Jamie Cameron <jca...@we...> wrote: > > >>>write(1, "Do you want to retry the same ed"..., 36) = 36 >>>read(0, "", 4096) = 0 >>>write(2, "Enter Y or N\n", 13) = 13 >>>write(1, "Do you want to retry the same ed"..., 36) = 36 >>>read(0, "", 4096) = 0 >>>write(2, "Enter Y or N\n", 13) = 13 >>>write(1, "Do you want to retry the same ed"..., 36) = 36 >>>read(0, "", 4096) = 0 >> >>That does explain quite a lot actually.. When you select the new 'Run >>on selected schedule' option, Webmin uses a special schedule format in >> the crontab file like @hourly or @monthly, which is only supported >>by Vixie-cron. However, your system doesn't seem to be using >>Vixie-cron, and so is choking on that schedule format .. And clearly >>the module needs to handle this kind of failure better, instead of >>letting cron go into an infinite loop! >> >>Which Linux distribution are you running there? I had assumed that all >> Linux variants came with Vixie-cron, except Trustix. > > > To be verbose ... > > webmin/software > -> Search for cron > --> anacron 2.3-17 > --> crontabs 1.10-1 > --> vixie-cron 3.0.1-63 > > webmin/webmin/edit_os.cgi > -> Redhat Linux 7.2 > > webmin/config.cgi?cron > > -> Supports Vixie-Cron extensions? - Yes > -> Path to Vixie-Cron system crontab file - /etc/crontab > > I will send you other details via feedback if necessary ... What happens if you run crontab -e at some user and add a cron job like : @hourly ls -l >/dev/null Does it accept the cron job, or complain that the new line is not valid? - Jamie |