search for: upsmon_pid

OK, can someone tell me what utterly moronic thing I am doing wrong? I have two roughly identical Linux system running NUT, and one works properly. The other almost does. The second system works well once everything is up, but after booting, the system does not have connectivity to the UPS. I have to manually run `upsdrvctl start backup`, `/etc/init.d/nut start`, and `upsd` to get NUT

...o upsd and upsmon and used it. #! /bin/sh # # nut - Script to start and stop Network UPS Tools daemons PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin NAME=nut DESC="Network UPS Tools" DEFAULT=/etc/default/nut [ -f $DEFAULT ] || exit 0 . $DEFAULT pid_dir=/var/run/nut upsmon_pid=${pid_dir}/upsmon.pid upsd_pid=${pid_dir}/upsd.pid upsd=/usr/local/ups/sbin/upsd upsmon=/usr/local/ups/sbin/upsmon upsdrvctl=/usr/local/ups/bin/upsdrvctl log=">/dev/null 2>/dev/null" # Check if /var/run/nut exists and has the correct perms check_var_directory() { [ ! -d ${p...

...te: > Is /etc/init.d/nut-client a Bash/Dash script? Is it possible to add the option to > the call of the driver in this script? Looks like some options can be passed: /etc/init.d/nut-client is a dash script and when it is started or restarted, it executes: start-stop-daemon -S -q -p $upsmon_pid -x $upsmon \ -- $UPSMON_OPTIONS >/dev/null 2>&1 && return 0 || return 1 or simply, it runs $upsmon -- $UPSMON_OPTIONS as a daemon, with these vars defined in the head of the script: $upsmon = "/sbin/upsmon" $UPSMON_OPTIONS = "" $UPSMON_OPTION...

On Wed, 14 Oct 2015, Davide Baldini wrote: >> Is there any command in the list provided by "upscmd -l myups" which is >> accepted by this UPS? > > None of the command sin the list successfully completes, not even > beeper.toggle. It looks as if the problem is more general than turning off the UPS. The command mechanism is broken. > I added -q and -D to