Skip to contentSkip to conversation

How to find out which udev rule is applied?

DISCUSSION [email protected] 2 participants 2 messages Jan 29, 2007

lore
Share & tools
lore
#0 lore raw

First, I hope I'm on the right mailinglist for my question, and apologize if I'm not ...

How can I find out which rule (at least which rule file) udev uses to generate/assign device nodes?
udevmonitor doesn't give me much information on that.

To make myself clear, my actual problem:
I have a printer/scanner combo, which is working but one problem: Since some time ago, /dev/usb/lp0 is assigned to root:scanner instead of root:lp, causing cups to fail.

I already edited some rules files in hope to sort it out, but without success.

Now I'd like to find out which rule is actually used to create the device node, so I can either modify it or make my own rule setting the permissions.

Is there a way to achieve this?

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

#1 lore raw
Quoted 12 lines · On 1/29/07, [email protected] <[email protected]> wrote:

First, I hope I'm on the right mailinglist for my question, and apologize if I'm not ...

How can I find out which rule (at least which rule file) udev uses to generate/assign device nodes?
udevmonitor doesn't give me much information on that.

To make myself clear, my actual problem:
I have a printer/scanner combo, which is working but one problem: Since some time ago, /dev/usb/lp0 is assigned to root:scanner instead of root:lp, causing cups to fail.

Quoted 8 lines

I already edited some rules files in hope to sort it out, but without success.

Now I'd like to find out which rule is actually used to create the device node, so I can either modify it or make my own rule setting the permissions.

Is there a way to achieve this?

What does:
udevtest /sys/class/printer/lp0

print? If it shows the scanner gid, there must be a rule that assigns it. If not, blame pam_console or similar to mess up your permission after udev has created the node.

Kay

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel