[FS#4077] ERROR level instead of INFO level in syslog messages from BusyBox components (crond)

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#4077 - ERROR level instead of INFO level in syslog messages from BusyBox components (crond)
User who did this - Chris (chder)

----------
I noticed this as well when it confused me into thinking the cron was somehow failing to run.

I have openwrt forwarding to a syslog server and the logs viewer over there is showing "Severity: Error"

Taking a peek at logread on the router itself I get:


Tue Feb  1 21:45:00 2022 cron.err crond[1636]: USER root pid 22437 cmd flock -n /var/lock/persist.lock /etc/package-list/persist.sh
Tue Feb  1 21:50:00 2022 cron.err crond[1636]: USER root pid 22515 cmd flock -n /var/lock/persist.lock /etc/package-list/persist.sh
Tue Feb  1 21:55:00 2022 cron.err crond[1636]: USER root pid 22586 cmd flock -n /var/lock/persist.lock /etc/package-list/persist.sh
Tue Feb  1 22:00:00 2022 cron.err crond[1636]: USER root pid 22664 cmd flock -n /var/lock/persist.lock /etc/package-list/persist.sh


According to ps crond is running with:

/usr/sbin/crond -f -c /etc/crontabs -l 8



root at ROUTER:~# crond --help
+ crond --help
BusyBox v1.33.2 (2022-01-23 10:30:30 UTC) multi-call binary.

Usage: crond [-fbS] [-l N] [-L LOGFILE] [-c DIR]

        -f      Foreground
        -b      Background (default)
        -S      Log to syslog (default)
        -l N    Set log level. Most verbose 0, default 8
        -L FILE Log to FILE
        -c DIR  Cron dir. Default:/etc/crontabs


----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4077#comment10500

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.