Mailinglist Archive: opensuse-bugs (6366 mails)
| < Previous | Next > |
[Bug 270252] New: invalid entry causes cron to stop registering crontable changes
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 1 May 2007 07:00:37 -0600 (MDT)
- Message-id: <bug-270252-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=270252
Summary: invalid entry causes cron to stop registering crontable
changes
Product: SUSE Linux 10.1
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: nohezp@xxxxxxxxx
QAContact: qa@xxxxxxx
We have noticed a problem with cron. After submitting a invalid cron
entry the daemon ignores any further changes to any cron tables. A
restart of cron fixes this behaviour until the next invalid entry is
submitted. To explain this lets say a user submits a cron entry:
* * * * mon-fri (/path/to/command)
The above entry is invalid as the manpage clearly mentions that "Ranges
or lists of names are not allowed." in day of week column.
But crontab accepts this silently and henceforth any change by any
user is ignored till crond is restarted. Which implies that any user
can trigger this bug and cause changes made by other users to their
respective cron tables to be ignored. Removing this invalid entry does
not fix the problem. cron has to be restarted.
We know that this bug exists in the following:
OpenSuSE 10.1 - cron-4.1-45.7.x86-64
OpenSuSE 10.3 - cron-4.1-88.i586
--
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.
Summary: invalid entry causes cron to stop registering crontable
changes
Product: SUSE Linux 10.1
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: nohezp@xxxxxxxxx
QAContact: qa@xxxxxxx
We have noticed a problem with cron. After submitting a invalid cron
entry the daemon ignores any further changes to any cron tables. A
restart of cron fixes this behaviour until the next invalid entry is
submitted. To explain this lets say a user submits a cron entry:
* * * * mon-fri (/path/to/command)
The above entry is invalid as the manpage clearly mentions that "Ranges
or lists of names are not allowed." in day of week column.
But crontab accepts this silently and henceforth any change by any
user is ignored till crond is restarted. Which implies that any user
can trigger this bug and cause changes made by other users to their
respective cron tables to be ignored. Removing this invalid entry does
not fix the problem. cron has to be restarted.
We know that this bug exists in the following:
OpenSuSE 10.1 - cron-4.1-45.7.x86-64
OpenSuSE 10.3 - cron-4.1-88.i586
--
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.
| < Previous | Next > |