search for: l1011

...ob/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 manipul...

...upstools/nut/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-groun...

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