https://bugzilla.novell.com/show_bug.cgi?id=270252 nohezp@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nohezp@gmail.com ------- Comment #1 from nohezp@gmail.com 2007-05-03 00:20 MST ------- I had forwarded a copy of bug report to the author of cron software. Reply from his team member is attached below. --------------------------- From: Phil M Perry Cc: Paul Vixie Subject: [Fwd: re: Nohez: invalid entry causes cron to stop registering crontable changes] Hello Nohez, This is Phil Perry. Paul Vixie has asked me to take a look at your problem with cron (invalid input causes all further crontab changes to be ignored until cron is restarted). I have been trying to replicate your reported problem, without success. Could you give me all the particulars of a case which exhibits this behavior? Is it root or a regular user that is editing the crontab, what field values are used, and what is the command? I need this for the two or more users involved (of course, please make them as generic as possible -- I don't want to know any proprietary or confidential information). Incidentally, it appears that "mon-fri" works fine for the day-of-week field -- apparently the crontab(5) man page needs updating. Every time I've tried it, an invalid field entry is rejected, and I'm asked if I want to re-edit the entry. I'm editing via the "crontab -e" command -- are you doing anything different? If you're directly editing crontab files (not using crontab -e), you're missing the validation checks that crontab provides. If you have a legitimate need to bypass crontab, we can look into beefing up the error checking in cron itself. Can you provide me with an invalid entry that is silently accepted? My cron is the 4.1 version provided with ftp.isc.org/isc/cron/cron_4.1.shar and dated 23 January 2004. Is there any way to tell if OpenSuSE has modified cron before compiling and shipping it? (You might ask as part of your bugzilla report.) You might try, just for kicks, downloading the cron 4.1 package from the ISC site and trying a build and install on your system. It was pretty simple on mine (Ubuntu 5.10) -- just "sh cron_4.1.shar", "make", and "make install". You'll probably want to comment out the Makefile lines to replace the man pages, and to save your existing /usr/sbin/cron and /usr/bin/crontab binary files someplace safe. I had to "touch /var/cron/cron.deny" to permit non-root users to edit their crontabs. Then you can see if the problem still exists. If it doesn't, there's something peculiar about OpenSuSE's copy. If it does, I will need more information on just what triggers the problem. I await your reply. regards, Phil -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=270252 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |nohezp@gmail.com ------- Comment #2 from mkoenig@novell.com 2007-05-09 06:29 MST ------- I can not reproduce this. Obviously ranges with day of week names are not illegal, this should be fixed in the documentation. I have not been able to create a invalid crontab entry which triggers the behaviour you described. Please provide an invalid entry that triggers the described behaviour. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.