Date: Thu, 03 Sep 2015 01:36:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 202863] sysutils/apcupsd faulty pid handling Message-ID: <bug-202863-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202863 Bug ID: 202863 Summary: sysutils/apcupsd faulty pid handling Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: itetcu@FreeBSD.org Reporter: aepalea@gmail.com Flags: maintainer-feedback?(itetcu@FreeBSD.org) Assignee: itetcu@FreeBSD.org I was trying to hack multiple UPS support by duplicating /usr/local/etc/rc.d/apcupsd under several distinct names and I got into a world of hurt with the pid file, which I traced down the pidfile variable not being passed to the apcupsd executable. I was able to fix this omission by adding one line, as below: pidfile="/var/run/apcupsd_Fred.pid" # MODIFIED PID FILE NAME required_files="/usr/local/etc/apcupsd/apcupsd.conf" command_args="-P $pidfile" # PROPOSED ADDITIONAL LINE command="/usr/local/sbin/apcupsd" After adding this line, pid file sanity returned to my particular hackish endeavour. This might be the totally wrong solution to my problem, but nevertheless the PID handling should work as advertised. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202863-13>