On 9/28/2012 11:02 AM, Lars Müller wrote:
On Fri, Sep 28, 2012 at 03:50:25PM +0200, Per Jessen wrote:
Since we switched to cronie in openSUSE 11.4, cron has been writing logmessages with the name of the executable in upper case, where as the previous cron daemon wrote in lower case.
I opened: https://bugzilla.novell.com/show_bug.cgi?id=3D780237
Vojtech (the maintainer) doesn't think this regression should be fixed, and closed it as WONTFIX. I think this regression should be fixed, even if nobody else has noticed it in 11.4 and 12.1.
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
It's to determine if a log message is caused by a child process or from the daemon.
Such an indication is a fine idea. Doing it by lying is not. Add markup characters or something but don't write untruths.
It looks like our man page is not up to date.
As this has not been noticed for two full release cycles the issue can't be this important.
Well, no, the release cycles are idiotically short now, and just because people haven't bothered to report a problem, or that a problem hasn't actually been severe enough to kill a baby, does not mean it's fine to just leave something knowingly broken. For my part, my systems have been running well enough that I haven't had occasion lately to read my logs. Only when I have some reason to even read the logs would I discover that they contained lies. When that happened, maybe I still wouldn't report it because maybe I have other things to do that day and maybe I've been discouraged by previous experiences exactly like this where reported problems were disregarded.
Reverting the change without any further discussion with the cron autors I consider as the wrong approach.
No you need to do _both_ that's why we have such a great patch maintenance system via obs and spec files. Until upstream fixes it, we fix it for ourselves just like we do countless other things, or we don't use that upstream package in the first place since it has broken behavior and that broken behavior is not even considered broken by the author, therefore will never be fixed and we don't want to maintain custom patches forever if we can avoid it.
Wontfix might not be the correct resolution reason. I consider this a feature and not a bug.
Please feel free to file a submit request to enhance the documentation/ man page.
Even if the documentation does not describe the purpose of this behavior, it's still not primarily a documentation error. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org