search for: syslogbit_set

...so continue logging to stderr with messages > landing into systemd journal or SMF service-instance log file. ok - netbsd doesn't do that (expecting things to daemonize and use syslog), but good to know. > A few programs are more explicit about this, e.g.: > ```` > :; git grep -n syslogbit_set > common/common.c:130:void syslogbit_set(void) > include/common.h:234:void syslogbit_set(void); > > clients/upssched.c:1341: syslogbit_set(); > drivers/main.c:1052: syslogbit_set(); > server/upsd.c:1827: syslogbit_set(); > ```` I did find that in drivers/...

...ike SMF or systemd can remain in "foreground" mode (with backgrounding handled by framework forking itself), so continue logging to stderr with messages landing into systemd journal or SMF service-instance log file. A few programs are more explicit about this, e.g.: ```` :; git grep -n syslogbit_set common/common.c:130:void syslogbit_set(void) include/common.h:234:void syslogbit_set(void); clients/upssched.c:1341: syslogbit_set(); drivers/main.c:1052: syslogbit_set(); server/upsd.c:1827: syslogbit_set(); ```` > So upsdebugx should therefore 1) not have the driver nam...

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