Bug 65134

Summary: snmptrapd init script complains about bad interpreter - invisible carriage returns in script
Product: [Retired] Red Hat Linux Reporter: ipvcor
Component: ucd-snmpAssignee: Phil Knirsch <pknirsch>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-18 00:14:38 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 ipvcor 2002-05-18 00:05:39 UTC 
Description of Problem:

The snmptrapd init script (/etc/rc.d/init.d/snmptrapd) contains invisible
carriage returns which produces the following error message when executed:

[root@machine init.d]# /etc/init.d/snmptrapd start
: bad interpreter: No such file or directory

Problem can be overcome by stripping all "/r"'s from the init script.


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


Red Hat Linux release 7.3 (Valhalla)

How Reproducible:

Always


Steps to Reproduce:
1. As root, type '/etc/init.d/snmptrapd start'
2. 
3. 

Actual Results:

Produces the following error:
: bad interpreter: No such file or directory


Expected Results:

Should start daemon


Additional Information:

n/a
Comment 1 ipvcor 2002-05-18 00:07:35 UTC 
Correction for the following section:


Version-Release number of selected component (if applicable):
ucd-snmp-4.2.4-3
Comment 2 ipvcor 2002-05-18 00:14:32 UTC 
quick fix instructions--

As root, perform the follwoing steps:

1. cd /etc/init.d/
2. dos2unix snmptrapd
3. chmod +x snmptrapd
4. touch /etc/snmp/snmptrapd
5. ./snmptrapd start
Comment 3 Phil Knirsch 2002-05-21 11:53:23 UTC 
Argh, what a stupid bug of mine! Fixing immediately in the package.

Thanks for catching it. Fixed in next version.

Read ya, Phil