Bug 59296 - snmpd initcripts creates useless pidfile
Summary: snmpd initcripts creates useless pidfile
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ucd-snmp
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-04 20:19 UTC by rm0
Modified: 2015-03-05 01:10 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2002-02-25 12:52:30 UTC


Attachments (Terms of Use)

Description rm0 2002-02-04 20:19:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
the snmpd Sys V init script shipped in the rpm 
create/deletes a /var/run/snmpd file at start/stop  
time.

The findpid* sh functions in /etc/init.d/functions 
expect pidfiles with filenames ending in .pid


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. # /sbin/service snmpd stop
2. inspect /var/run dir. Several .pid files for the different
   services are present
3. # /sbin/service snmpd start
4. inspect /var/run again.

Actual Results:  A 'snmpd' file now exists


Expected Results:  It should be named snmpd.pid. both for sanity and uniformity

Additional info:

The problem affects packages shipped w/previous releases of the 
OS too, as well as their errata upgrades and the current post-7.2 
Rawhide package.

It would be nice to check all the Sys V initscripts in a full 
RHL 7.2 install (or with a tool that can extract all the 
/etc/.*init.d/ files from a full package repository and grep 
them all for the "/var/run" token) to ensure no similar problems 
exist in other packages.

Comment 1 Phil Knirsch 2002-02-25 12:52:25 UTC
Will be changed in next package.

Read ya, Phil

Comment 2 Phil Knirsch 2002-04-09 12:41:36 UTC
Fixed in ucd-snmp-4.2.4.pre3-5 available via rawhide real soon now... :-)

Read ya, Phil


Note You need to log in before you can comment on or make changes to this bug.