Bug 129340

Summary: resmgr errors in /var/log/messages
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Andreas Vetter <vetter>
Component: OtherAssignee: Juergen Weigert <jw>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: asklein
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Vetter 2005-10-19 12:01:01 UTC 
resmgr logs errors to /var/log/messages:
Oct  7 00:21:51 pluto resmgr[4824]: set_facl() - ACL error on /dev/parport4,
acl_set_file: No such file or directory
Oct  7 00:21:51 pluto resmgr[4824]: set_facl() - ACL error on /dev/parport5,
acl_set_file: No such file or directory
Oct  7 00:21:51 pluto resmgr[4824]: set_facl() - ACL error on /dev/parport6,
acl_set_file: No such file or directory
Oct  7 00:21:51 pluto resmgr[4824]: set_facl() - ACL error on /dev/parport7,
acl_set_file: No such file or directory

Reason is:
/dev/parport4, 5, 6 and 7 do not exist.
But in /etc/resmgr.conf.d/99-uisp_parport.conf these devices are added:
add /dev/parport4 desktop
add /dev/parport5 desktop
add /dev/parport6 desktop
add /dev/parport7 desktop
Comment 1 Ludwig Nussel 2005-10-19 13:53:35 UTC 
Harmless. It's a minor bug that such messages also appear when logging out. Will be fixed in case an update needs to be done for another reason.

Where does /etc/resmgr.conf.d/99-uisp_parport.conf come from? You may append noacl on each line to prevent resmgr from trying to install file acls. You may also use HAL to have them added only when the device nodes actually appear.
Comment 2 Andreas Vetter 2005-10-19 13:58:48 UTC 
# rpm -qf /etc/resmgr.conf.d/99-uisp_parport.conf
uisp-20050207suse-2
Comment 3 Ludwig Nussel 2005-10-19 14:11:10 UTC 
Hrmpf. Not exactly what it was intended for. Fortunately /dev/parport* is not in hal on 10.0 yet. Jürgen: we need to handle that differently. I don't think it's a good idea to give every user access to parallel ports just because a random package got installed. If it's really necessary to grant access there I'd introduce a new ressource class for which users _don't_ have access to by default but can easily add themselves. HAL has to carry info about parport then as well. You don't have to and should not ship a resmgr config file then (except maybe with a commented line how to add yourself to the ressource class).
Comment 4 Juergen Weigert 2005-10-19 14:28:23 UTC 
Sure, open to suggestions. I did it the most primitive way.
Actually, uisp not always uses /dev/parport, it may also require a serial line, depending on commandline parameters. But accessing parallel or serial devices is essential for uisp, that is its purpose, so I'd like to make the process transparent to the user. 

Currently it would say 
'/dev/parport0: Permission denied
Failed to open ppdev.'

How do I guide the user so that he is not stuck with that message?
Comment 5 Juergen Weigert 2007-01-19 16:48:09 UTC 

*** This bug has been marked as a duplicate of bug 235059 ***