crond log level meaning
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I cannot find anywhere the log level meaning of crond
.
I know that 0 is pretty much "log everything" while 8 is "show only important info" thanks to the crond help:
/ # crond --help
BusyBox v1.26.2 (2017-11-23 08:40:54 GMT) multi-call binary.
Usage: crond -fbS -l N -d 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
-d N Set log level, log to stderr
-L FILE Log to FILE
-c DIR Cron dir. Default:/var/spool/cron/crontabs
but where I can find exactly the documentation/meaning about the different levels?
I'm on Alpine 3.6.
cron logs alpine-linux
add a comment |Â
up vote
2
down vote
favorite
I cannot find anywhere the log level meaning of crond
.
I know that 0 is pretty much "log everything" while 8 is "show only important info" thanks to the crond help:
/ # crond --help
BusyBox v1.26.2 (2017-11-23 08:40:54 GMT) multi-call binary.
Usage: crond -fbS -l N -d 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
-d N Set log level, log to stderr
-L FILE Log to FILE
-c DIR Cron dir. Default:/var/spool/cron/crontabs
but where I can find exactly the documentation/meaning about the different levels?
I'm on Alpine 3.6.
cron logs alpine-linux
Tryman cron
. Values may differ depending on your OS/cron version.
â ridgy
Dec 24 '17 at 13:38
Unfortunately on Alpine there is no man. I installed withapk add man man-pages
, but still when I doman cron
orman crond
it says "man: No entry for crond/cron in the manual."
â Oscar Fanelli
Dec 24 '17 at 19:40
OK sorry. I don't know Alpine. so I can't help any futher.
â ridgy
Dec 24 '17 at 21:08
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I cannot find anywhere the log level meaning of crond
.
I know that 0 is pretty much "log everything" while 8 is "show only important info" thanks to the crond help:
/ # crond --help
BusyBox v1.26.2 (2017-11-23 08:40:54 GMT) multi-call binary.
Usage: crond -fbS -l N -d 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
-d N Set log level, log to stderr
-L FILE Log to FILE
-c DIR Cron dir. Default:/var/spool/cron/crontabs
but where I can find exactly the documentation/meaning about the different levels?
I'm on Alpine 3.6.
cron logs alpine-linux
I cannot find anywhere the log level meaning of crond
.
I know that 0 is pretty much "log everything" while 8 is "show only important info" thanks to the crond help:
/ # crond --help
BusyBox v1.26.2 (2017-11-23 08:40:54 GMT) multi-call binary.
Usage: crond -fbS -l N -d 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
-d N Set log level, log to stderr
-L FILE Log to FILE
-c DIR Cron dir. Default:/var/spool/cron/crontabs
but where I can find exactly the documentation/meaning about the different levels?
I'm on Alpine 3.6.
cron logs alpine-linux
edited Dec 31 '17 at 15:20
Jeff Schaller
31.8k848109
31.8k848109
asked Dec 24 '17 at 13:21
Oscar Fanelli
1134
1134
Tryman cron
. Values may differ depending on your OS/cron version.
â ridgy
Dec 24 '17 at 13:38
Unfortunately on Alpine there is no man. I installed withapk add man man-pages
, but still when I doman cron
orman crond
it says "man: No entry for crond/cron in the manual."
â Oscar Fanelli
Dec 24 '17 at 19:40
OK sorry. I don't know Alpine. so I can't help any futher.
â ridgy
Dec 24 '17 at 21:08
add a comment |Â
Tryman cron
. Values may differ depending on your OS/cron version.
â ridgy
Dec 24 '17 at 13:38
Unfortunately on Alpine there is no man. I installed withapk add man man-pages
, but still when I doman cron
orman crond
it says "man: No entry for crond/cron in the manual."
â Oscar Fanelli
Dec 24 '17 at 19:40
OK sorry. I don't know Alpine. so I can't help any futher.
â ridgy
Dec 24 '17 at 21:08
Try
man cron
. Values may differ depending on your OS/cron version.â ridgy
Dec 24 '17 at 13:38
Try
man cron
. Values may differ depending on your OS/cron version.â ridgy
Dec 24 '17 at 13:38
Unfortunately on Alpine there is no man. I installed with
apk add man man-pages
, but still when I do man cron
or man crond
it says "man: No entry for crond/cron in the manual."â Oscar Fanelli
Dec 24 '17 at 19:40
Unfortunately on Alpine there is no man. I installed with
apk add man man-pages
, but still when I do man cron
or man crond
it says "man: No entry for crond/cron in the manual."â Oscar Fanelli
Dec 24 '17 at 19:40
OK sorry. I don't know Alpine. so I can't help any futher.
â ridgy
Dec 24 '17 at 21:08
OK sorry. I don't know Alpine. so I can't help any futher.
â ridgy
Dec 24 '17 at 21:08
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
The particular semantics of the log level values for crond
are only defined in the code, it seems. All of the crond
logging there goes through a crondlog()
function in busybox/miscutils/crond.c
function:
static void crondlog(unsigned level, const char *msg, va_list va)
{
if (level >= G.log_level) {
/* Do logging... */
So that only those messages with levels higher than the one you specify via the -l
command-line option are logged.
Then, elsewhere in that crond.c
file, we see that crondlog()
is only called via the log5()
, log7()
, and log8()
wrapper functions. Which means that those are the only levels at which that crond
program logs messages.
These log levels are specific to crond
, and are not related to any syslog(3)
levels or other programs. In short, the meaning of these levels is only found in the source code for this program.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
The particular semantics of the log level values for crond
are only defined in the code, it seems. All of the crond
logging there goes through a crondlog()
function in busybox/miscutils/crond.c
function:
static void crondlog(unsigned level, const char *msg, va_list va)
{
if (level >= G.log_level) {
/* Do logging... */
So that only those messages with levels higher than the one you specify via the -l
command-line option are logged.
Then, elsewhere in that crond.c
file, we see that crondlog()
is only called via the log5()
, log7()
, and log8()
wrapper functions. Which means that those are the only levels at which that crond
program logs messages.
These log levels are specific to crond
, and are not related to any syslog(3)
levels or other programs. In short, the meaning of these levels is only found in the source code for this program.
add a comment |Â
up vote
2
down vote
accepted
The particular semantics of the log level values for crond
are only defined in the code, it seems. All of the crond
logging there goes through a crondlog()
function in busybox/miscutils/crond.c
function:
static void crondlog(unsigned level, const char *msg, va_list va)
{
if (level >= G.log_level) {
/* Do logging... */
So that only those messages with levels higher than the one you specify via the -l
command-line option are logged.
Then, elsewhere in that crond.c
file, we see that crondlog()
is only called via the log5()
, log7()
, and log8()
wrapper functions. Which means that those are the only levels at which that crond
program logs messages.
These log levels are specific to crond
, and are not related to any syslog(3)
levels or other programs. In short, the meaning of these levels is only found in the source code for this program.
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
The particular semantics of the log level values for crond
are only defined in the code, it seems. All of the crond
logging there goes through a crondlog()
function in busybox/miscutils/crond.c
function:
static void crondlog(unsigned level, const char *msg, va_list va)
{
if (level >= G.log_level) {
/* Do logging... */
So that only those messages with levels higher than the one you specify via the -l
command-line option are logged.
Then, elsewhere in that crond.c
file, we see that crondlog()
is only called via the log5()
, log7()
, and log8()
wrapper functions. Which means that those are the only levels at which that crond
program logs messages.
These log levels are specific to crond
, and are not related to any syslog(3)
levels or other programs. In short, the meaning of these levels is only found in the source code for this program.
The particular semantics of the log level values for crond
are only defined in the code, it seems. All of the crond
logging there goes through a crondlog()
function in busybox/miscutils/crond.c
function:
static void crondlog(unsigned level, const char *msg, va_list va)
{
if (level >= G.log_level) {
/* Do logging... */
So that only those messages with levels higher than the one you specify via the -l
command-line option are logged.
Then, elsewhere in that crond.c
file, we see that crondlog()
is only called via the log5()
, log7()
, and log8()
wrapper functions. Which means that those are the only levels at which that crond
program logs messages.
These log levels are specific to crond
, and are not related to any syslog(3)
levels or other programs. In short, the meaning of these levels is only found in the source code for this program.
answered Dec 31 '17 at 18:13
Castaglia
4111411
4111411
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f412805%2fcrond-log-level-meaning%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Try
man cron
. Values may differ depending on your OS/cron version.â ridgy
Dec 24 '17 at 13:38
Unfortunately on Alpine there is no man. I installed with
apk add man man-pages
, but still when I doman cron
orman crond
it says "man: No entry for crond/cron in the manual."â Oscar Fanelli
Dec 24 '17 at 19:40
OK sorry. I don't know Alpine. so I can't help any futher.
â ridgy
Dec 24 '17 at 21:08