From owner-freebsd-ports-bugs@freebsd.org  Thu Sep  3 01:36:11 2015
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EF009C8094
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Thu,  3 Sep 2015 01:36:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6B217129B
 for <freebsd-ports-bugs@FreeBSD.org>; Thu,  3 Sep 2015 01:36:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t831aBAQ087764
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 3 Sep 2015 01:36:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 202863] sysutils/apcupsd faulty pid handling
Date: Thu, 03 Sep 2015 01:36:11 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: aepalea@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: itetcu@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 flagtypes.name
Message-ID: <bug-202863-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Sep 2015 01:36:11 -0000

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.