search for: upsd_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

...! /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 ${pid_dir} ] && mkdir -p $...

2015-03-26 9:03 GMT+01:00 Arnaud Quette <arnaud.quette at gmail.com>: > Hey mister M' > > A first huge thanks for taking care of this, and so late in the night. I > know that it's not easy... > > (sent from my S3... please excuse my brevity) > Le 25 mars 2015 18:49, "Emilien Kia" <kiae.dev at gmail.com> a ?crit : > > > > > >

.... > But it is a little bit out of my competencies (I am not a bash and > linux-init-process expert). > I'm running Ubuntu Server 14.04 in all the servers I maintain and also use NUT. The process is started with the following command in /etc/init.d/nut-server: start-stop-daemon -S -p $upsd_pid -x $upsd \ -- $UPSD_OPTIONS >/dev/null 2>&1 && log_progress_msg "upsd" || log_progress_msg "(upsd failed)" and obviously, a backslash is missing on the second line! (line 83 on the real script) So even if it fails, the next command (log_process_msg) will a...