From: Martin M. <mar...@de...> - 2003-09-25 05:31:41
|
Hi Jamie, Jamie Cameron <jca...@we...> wrote: >> write(1, "Do you want to retry the same ed"..., 36) =3D 36 >> read(0, "", 4096) =3D 0 >> write(2, "Enter Y or N\n", 13) =3D 13 >> write(1, "Do you want to retry the same ed"..., 36) =3D 36 >> read(0, "", 4096) =3D 0 >> write(2, "Enter Y or N\n", 13) =3D 13 >> write(1, "Do you want to retry the same ed"..., 36) =3D 36 >> read(0, "", 4096) =3D 0 > >That does explain quite a lot actually.. When you select the new 'Run=20 >on selected schedule' option, Webmin uses a special schedule format in=20 > the crontab file like @hourly or @monthly, which is only supported=20 >by Vixie-cron. However, your system doesn't seem to be using=20 >Vixie-cron, and so is choking on that schedule format .. And clearly=20 >the module needs to handle this kind of failure better, instead of=20 >letting cron go into an infinite loop! > >Which Linux distribution are you running there? I had assumed that all=20 > 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 ... kind regards Martin Mewes --=20 Novacote Flexpack - Division of COIM Deutschland GmbH c/o IT/IS-Department - Hamburg - Germany |