Red Hat Bugzilla – Bug 70712
irda initscript has wrong error handling
Last modified: 2015-01-07 18:58:35 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721 Description of problem: [peterve@limbo-pc init.d]$ ./irda start touch: creating `/var/lock/subsys/irda': Toegang geweigerd [ OK ] Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. as a normal user "irda start" 2. 3. Actual Results: touch: creating `/var/lock/subsys/irda': Toegang geweigerd [ OK ] Expected Results: touch: creating `/var/lock/subsys/irda': Toegang geweigerd [FAILED] Additional info: Source RPM: irda-utils-0.9.14-6.src.rpm
Still occurs in Red Hat Linux 8.0.
You can't restart services as a normal user. That's not limited to irda.
With this Bugzilla report I specifically meant the exit handling of this initscript. The use of "/etc/rc.d/init.d/irda start" as a normal user results in the following strange error : touch: cannot touch `/var/lock/subsys/irda': Permission deniedOK ' It would be 'tidier' to patch the script as follows : < echo -n $"Starting $prog: " < daemon /usr/sbin/irattach ${DEVICE} ${ARGS} < touch /var/lock/subsys/irda < echo --- > ID=`id -u` > if [ $ID -eq 0 ]; then > echo -n $"Starting $prog: " > daemon /usr/sbin/irattach ${DEVICE} ${ARGS} > touch /var/lock/subsys/irda > echo > else > echo $"You need to be root to start this script ! " > fi Of course, this is only for the start parameter of the script, but if the script is called this way (a a normal user) it will at least give a proper error message.