Version: 3.2.2 (using KDE 3.2.2, (testing/unstable)) Compiler: gcc version 3.3.3 (Debian 20040401) OS: Linux (i686) release 2.4.26+grsec.ccs.48 I use Kcron for years, and the kde3 version seemed to behave perfectly, except it didn't save anything (no error msg, and closing kcron leads to loss of modifications or new entries). I went back to 'crontab -e' to add an entry, and received the following message "/tmp/crontab.Sk1gYb/crontab":17: bad minute : I had -0 as minutes in some old entry. This corrected, crontab was happy, and kcron saving worked again. I don't know how this -0 came in, as I didn't use anything else than kcron on this system (bug of an old version ?). Anyway, kcron should at least complain that it couldn't update the crontab. Thanks for this nice tool,
The '-' comes if you check the 'silent' box. It's a vixie cron extension. What version of cron does your system use? I'm not sure if vixie cron is a requirement - I'll look into it and see if I should make kcron handle non-extended crons. Probably should.
This is the default cron of Debian, so the one from Paul Vixie according to the names that I find in the docs. choupi:# apt-cache policy cron cron: Installés : 3.0pl1-86 Candidat : 3.0pl1-86 Table de version : *** 3.0pl1-86 0 600 http://ftp.de.debian.org sarge/main Packages 99 http://ftp.uk.debian.org sid/main Packages 100 /var/lib/dpkg/status But you pointed the problem: in kcron, if I try to check "Silent", I get an error message when saving (something like "Can't save, error occured" in English). On the console I get this again: christ@choupi:~$ kcron "/tmp/kde-christ/kcrono0U3Tb.tmp":13: bad minute errors in crontab file, can't install. If I try to add the '-' via crontab -e, it fails: christ@choupi:~$ crontab -e crontab: installing new crontab "/tmp/crontab.OE0cgL/crontab":19: bad minute errors in crontab file, can't install. Do you want to retry the same edit? n This is now in kcron 3.2.3.
Would you be able to post the content of the crontab file? (blocking out any security sensitive stuff of course). (I won't reply for a while - I'm off to the Baltics for a fortnight).
This is the complete file. BTW, the problem is there when I use kcron on a user which has never used cron. christ@choupi:~$ crontab -l # Signature #\-0 * * * * /home/christ/bin/MakeSig >/dev/null # MAJ spams 0 12,13 * * * sa-learn --mbox --spam ~/Vrac/spam && sa-learn --mbox --ham ~/Vrac/ham # Mise à jour sites #\-0 1,6 * * * sitecopy --update -a # Sauvegardes 5 2,20 * * * /home/christ/bin/Sauvegardes # Génération fichier des tags 0 19 * * * /home/christ/bin/MakeTagsCompil # Apt Show Version #\0 22 * * * /home/christ/bin/aptshowversions # Compare Img 0 1 * * * /home/christ/bin/cmpImg # Regénération site murphyque 0 4 * * * /home/christ/public_html/Murphy.dyn/totale yes # Dailystrips 0 0,10,16,17,18,19 * * * dailystrips --random >~/dl.html 2>/dev/null # Maj liste MP3 0 22 * * * /home/christ/bin/MajMP3 # This file was written by KCron. Copyright (c) 1999, Gary Meyer # Although KCron supports most crontab formats, use care when editing. # Note: Lines beginning with "#\" indicates a disabled task.
*** Bug 128643 has been marked as a duplicate of this bug. ***
Confirming with KCron 3.5.3. I'm using Debian Sid with vixie-cron 3.0p11.
whattabout just removing the concept of 'silence' since it doesn't work many places anyway. /Sune
Created attachment 20104 [details] remove the concept of 'silent tasks' Hi! A quick patch that removes 'silent tasks'
Removed in KDE4