On 21:24 Sun 17 Oct , Anders Johansson wrote: <SNIP>
This is what I meant about non-printable garbage characters. cron can handle any number and mixture of spaces and tabs (must be at least one) between the entries, so if that procedure worked there had to be at least one character in there that wasn't space or tab but that still wasn't visible on screen.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Interesting you should mention that fact. I usually create new cron jobs directly in crontab & they work as expected. Once in awhile, however, I get a frelled job ...and usually I can go to kcron & look at it and find that the user might be '*' (for instance) and the command is root <expected command follows>. Looking at crontab tells me nothing but if I either correct it in kcron or crontab by the explained method, it will work. By the same token, I have had multiple problems using kcron to create a cron job. On most occasions the job gets messed up when I save it from kcron whereas I found that if I enter the job directly into crontab the chance that something will not work is greatly reduced. I haven't a clue as to why, but this behaviour has been prevelant for a long, long time and nothing I tried --up to & including a clean install-- did any good. -- "Yogi" CH Namasté Yoga Studio