search for: l1205

...lan for bestfortress very much matches that, 1 to 5 where 5 is if you want to see every IO byte. > Regarding syslog/stdout/stderr, the upsdebugx*() methods are defined here > and near: > https://github.com/networkupstools/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...

...here" would be N+1 or more). De-facto verbosities fizzle out at 6, but generally it is an int value, so... Regarding syslog/stdout/stderr, the upsdebugx*() methods are defined here and near: https://github.com/networkupstools/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()...

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

On Thu, Feb 6, 2020 at 9:15 AM James Henderson <jh7370.2008 at my.bristol.ac.uk> wrote: > > On Thu, 6 Feb 2020 at 00:24, Jon Chesterfield via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> This doesn't sound right. GNU binutils have a large quantity of legacy >> cruft, not least the redundancy between tools like readelf and objdump >> which are