search for: nut_confpath

...ag) > { > *val |= flag; > @@ -440,51 +435,25 @@ > > > /* Return the default path for the directory containing configuration files */ > -const char * confpath(void) > +const char * confpath(void) > { > - const char * path; > - > - if ((path = getenv("NUT_CONFPATH")) == NULL) { > #ifndef WIN32 > - path = CONFPATH; > + const char *path = getenv("NUT_CONFPATH"); > #else > - if( relative_conf_path == NULL ) { > - path = getfullpath(PATH_ETC); > - if( path == NULL ) { > - path = CONFPATH; > - } > - } &gt...

Hi, I'm using the CGI program upsstats.cgi to view the status of UPS's on a web browser. I'd want to do something like that: /var/www/nut-cgi-bin-group-A/upsstats.cgi /var/www/nut-cgi-bin-group-B/upsstats.cgi /var/www/nut-cgi-bin-group-C/upsstats.cgi In that way using .htaccess I allow only certains IPs access to UPS from group A. How could I do that? Thanks in advance" --

...apted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'hear...

...apted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'hear...

...and script :D > Experimental debugging now sounds possible. > > (*) PC under the desk wails with all its cooling fans as soon as I started > the client which spawned a daemon and itself had exited: > > $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm > NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD > 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT command > m...

...and script :D > Experimental debugging now sounds possible. > > (*) PC under the desk wails with all its cooling fans as soon as I started > the client which spawned a daemon and itself had exited: > > $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm > NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD > 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the > 'heartbeat at localhost' we were launched to process? > 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT command > m...

...apted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'hear...

...apted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command the 'heartbeat at localhost' we were launched to process? 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT command matched the 'hear...

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

...rimental debugging now sounds possible. >> >> (*) PC under the desk wails with all its cooling fans as soon as I >> started the client which spawned a daemon and itself had exited: >> >> $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm >> NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD >> 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command >> the 'heartbeat at localhost' we were launched to process? >> 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT co...

...rimental debugging now sounds possible. >> >> (*) PC under the desk wails with all its cooling fans as soon as I >> started the client which spawned a daemon and itself had exited: >> >> $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT NUT_STATEPATH=/dev/shm >> NUT_CONFPATH=`pwd`/tests/NIT/tmp/etc ./clients/upssched -DDDDDDDD >> 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT command >> the 'heartbeat at localhost' we were launched to process? >> 0.000053 [D1] parse_at: 'heartbeat at localhost' in AT co...

Compiling against http://www.networkupstools.org/source/2.7/nut-2.7.4.tar.gz. I also have libusb-0.1-4 installed but no joy. On Mon, Mar 23, 2020 at 2:45 AM Jim Klimov <jimklimov at cos.ru> wrote: > On March 23, 2020 12:50:11 AM UTC, Tyler Montney <montneytyler at gmail.com> > wrote: > >Came across this in the process of troubleshooting: > > >

OpenWRT version 23.05.0-rc3 is, for starters, not supported anymore by the OpenWRT project, and is old. The current version is OpenWRT 23.05.05 The reason you are likely getting an old version of NUT when you load the nut package is because you are using an old version of openwrt. Your team needs to sysupdate your 4G LTE Wifi router You also, in my opinion, need to seriously reconsider