Bug 86256

Summary:	smpd init script has no error checking
Product:	[Retired] Red Hat Linux	Reporter:	Eric Wood <eric>
Component:	net-snmp	Assignee:	Phil Knirsch <pknirsch>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-11-19 10:45:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eric Wood 2003-03-18 13:57:34 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)

Description of problem:
The /etc/init.d/snmpd init script will always give you and "OK" even though the 
daemon really didn't start.  There is not enough error checking in this script 
like the more mature named and sendmail scripts have.

Version-Release number of selected component (if applicable):
net-snmp-5.0.1-6

How reproducible:
Always

Steps to Reproduce:
1. Create a bad snmp conf file.
2. service snmpd start

    

Actual Results:  [OK]

Expected Results:  [FAILED]

Additional info:

Comment 1 Phil Knirsch 2003-08-08 14:15:03 UTC

Well, i tried it with the latest net-snmp version (5.0.8-6), and no matter how i
garbled the snmpd.conf file the daemon still starts and is running. It might not
do anything useful, mind you, but it's up and running. :-)

Not sure if there is an option with "died when corrupt config file", cause thats
something i would certainly add.

Read ya, Phil

Comment 2 Phil Knirsch 2003-11-19 10:45:02 UTC

OK, beeh looking into it, there is no way to 'check' if the config
file is reasonable and the snmpd doesn't return any information about
it to the calling script, so i'm closing this bug as wontfix as it is
not fixable in a sane way.

Read ya, Phil