Bug 294061

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Install udev
2. Install zaptel
3. Install asterisk and configure it to run as the asterisk user
  
Actual results:
Observe as asterisk fails to access the zaptel devices because they're not
accessible to the asterisk user

Expected results:
udev should not include configuration for the zaptel devices, as configuration
for these devices in udev is already provided by the zaptel driver, and the
verson provided by the zaptel driver correctly sets the permissions to the
asterisk user.

Additional info:

The file /etc/udev/rules.d/50-udev.rules contains the following rules:

# Section for zaptel device
KERNEL="zapctl",     NAME="zap/ctl"
KERNEL="zaptimer",   NAME="zap/timer"
KERNEL="zapchannel", NAME="zap/channel"
KERNEL="zappseudo",  NAME="zap/pseudo"
KERNEL="zap[0-9]*",  NAME="zap/%n"

The zaptel driver installs /etc/udev/rules.d/zaptel.rules with the following:

# zaptel devices with ownership/permissions for running as non-root
KERNEL=="zapctl", NAME="zap/ctl", OWNER="asterisk", GROUP="asterisk", MODE="0660"
KERNEL=="zaptranscode", NAME="zap/transcode", OWNER="asterisk",
GROUP="asterisk", MODE="0660"
KERNEL=="zaptimer", NAME="zap/timer", OWNER="asterisk", GROUP="asterisk",
MODE="0660"
KERNEL=="zapchannel", NAME="zap/channel", OWNER="asterisk", GROUP="asterisk",
MODE="0660"
KERNEL=="zappseudo", NAME="zap/pseudo", OWNER="asterisk", GROUP="asterisk",
MODE="0660"
KERNEL=="zap[0-9]*", NAME="zap/%n", OWNER="asterisk", GROUP="asterisk", MODE="0660"

Since the zaptel driver provides its own rules file, this config should not be
included in the core udev ruleset at all.

Every time I get an update to udev since upgrading our asterisk server to rhel5,
I have to go comment those rules out of 50-udev.rules in order to get asterisk
to work.