Displaying 4 results from an estimated 4 matches for "upslog_stderr".
2023 Jan 15
1
logging strategy
...7e774c3f03a08228430143396e9/common/common.c#L1205
> and end up calling vupslog() at which can report to stderr (not stdout)
> and/or syslog, based on settings - see around
> https://github.com/networkupstools/nut/blob/ad70749f243527e774c3f03a08228430143396e9/common/common.c#L1011.
> The UPSLOG_STDERR bit is set by default, but cleared in the background()
> method, along with raising the UPSLOG_SYSLOG bit. By default enabled debug
> means staying foreground, so the bits are not changed. However "recently"
> the explicit -F/-B flags were added to manipulate fore-/back-grounding...
2023 Jan 15
1
logging strategy
...t/blob/ad70749f243527e774c3f03a08228430143396e9/common/common.c#L1205
and end up calling vupslog() at which can report to stderr (not stdout)
and/or syslog, based on settings - see around
https://github.com/networkupstools/nut/blob/ad70749f243527e774c3f03a08228430143396e9/common/common.c#L1011.
The UPSLOG_STDERR bit is set by default, but cleared in the background()
method, along with raising the UPSLOG_SYSLOG bit. By default enabled debug
means staying foreground, so the bits are not changed. However "recently"
the explicit -F/-B flags were added to manipulate fore-/back-grounding
independently...
2011 Jan 19
1
[nut-commits] svn commit r2845 - branches/windows_port/common
...====================================================
> --- branches/windows_port/common/common.c Tue Jan 18 15:40:58 2011 (r2844)
> +++ branches/windows_port/common/common.c Tue Jan 18 19:52:02 2011 (r2845)
> @@ -41,11 +41,6 @@
> int nut_log_level = 0;
> static int upslog_flags = UPSLOG_STDERR;
>
> -#ifdef WIN32
> -const char * relative_conf_path = NULL;
> -const char * relative_state_path = NULL;
> -#endif
> -
> static void xbit_set(int *val, int flag)
> {
> *val |= flag;
> @@ -440,51 +435,25 @@
>
>
> /* Return the default path for the di...
2023 Jan 15
1
logging strategy
I am looking at bestfortress and trying to figure out and fix some
things, which is causing me to try to improve logging first. A few
questions:
0) The developer guide doesn't seem to address any of this, or did I
miss it?
1) It seems upsdebugx prints to stdout instead of syslog if in
foreground. That's great but I didn't figure it out from docs.
2) I didn't find a plan for