Date: Thu, 30 Aug 2012 20:51:25 GMT From: "David A. Bright" <David_A_Bright@DELL.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/171192: pidfile_read should be made a public interface Message-ID: <201208302051.q7UKpPS8086503@red.freebsd.org> Resent-Message-ID: <201208302100.q7UL0Iko060119@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 171192 >Category: misc >Synopsis: pidfile_read should be made a public interface >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Aug 30 21:00:18 UTC 2012 >Closed-Date: >Last-Modified: >Originator: David A. Bright >Release: 9.1 >Organization: Dell Compellent >Environment: FreeBSD es-bb91-1 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r+90246d5: Tue Aug 14 08:58:06 CDT 2012 root@localhost.localdomain:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The libutil pidfile(3) routines are useful, but provide only an interface for creating pid files. For software that wants to read and extract a pid from a pid file, there is no public interface. However, the private (static) function pidfile_read() in pidfile.c would provide such an interface. It need only be made externally visible and documented. >How-To-Repeat: >Fix: Remove "static" from definition in pidfile.c. Add pidfile_read() prototype to libutil.h. Add pidfile_read() doc to pidfile.3. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208302051.q7UKpPS8086503>