Bug 70717

Summary: portmap initscript has wrong error handling
Product: [Retired] Red Hat Public Beta Reporter: Peter van Egdom <p.van.egdom>
Component: portmapAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED RAWHIDE QA Contact: Jay Turner <jturner>
Severity: low Docs Contact:
Priority: medium    
Version: limboCC: srevivo
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-08-04 14:47:06 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 Peter van Egdom 2002-08-04 14:47:02 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721

Description of problem:
"portmap start" as a normal user : 

[peterve@limbo-pc init.d]$ ./portmap start
Starting portmapper:                                       [  OK  ]
touch: creating `/var/lock/subsys/portmap': Toegang geweigerd


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


How reproducible:
Always

Steps to Reproduce:
1. "portmap start" as a normal user
2.
3.
	

Actual Results:
[peterve@limbo-pc init.d]$ ./portmap start
Starting portmapper:                                       [  OK  ]
touch: creating `/var/lock/subsys/portmap': Toegang geweigerd


Expected Results:
[peterve@limbo-pc init.d]$ ./portmap start
Starting portmapper:                                       [FAILED]
touch: creating `/var/lock/subsys/portmap': Toegang geweigerd


Additional info:

Source RPM: portmap-4.0-45.src.rpm
Comment 1 Trond Eivind Glomsrxd 2002-08-06 20:54:22 UTC 
Fixed in portmap-4.0-46