Bug 188139

Summary: run program's error not captured at default log level (err)
Product: [Fedora] Fedora Reporter: Richard Kennedy <richard>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: kay.sievers
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-28 05:38:40 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
patch of possible solution none

Description Richard Kennedy 2006-04-06 08:06:11 EDT
Description of problem:

I've created a custom udev rule to run a script to initialise & load firmware
for an prism2 wlan usb card.
At the default log level, udevd discards any error output from the script making
it difficult for normal users to understand why their wlan device isn't working
if there's a failure. there is no output logged even if the script return an
error code. 

Pleas enhance udev to log STDERR for all RUN rules.    

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


How reproducible:

Steps to Reproduce:
1. load prism2_usb device
2. udevd runs script that errors
3. script errors are not logged
Actual results:

No errors logged
Expected results:

Additional info:
The prism2_usb driver is an out of kernel driver for this wlan card.
{see  http://www.linux-wlan.com/linux-wlan/}

Looking at the source code, can I just change the run_program(...) call in
udev_rules.c as in the attached patch, to get the behaviour I want?
patch _NOT_ tested!

Are there any instructions for building udevd from the src.rpm ? I guess a apply
all the patches in the rpm and build as normal ?
Comment 1 Richard Kennedy 2006-04-06 08:06:11 EDT
Created attachment 127407 [details]
patch of possible solution
Comment 2 Kay Sievers 2006-04-09 09:10:22 EDT
The behavior is intentional, as some tools validly print errors, or are even
expected to fail while called from udev. It would needlessly flood the syslog.
The log level of the udev daemon can be changed at runtime if needed for
debugging with:
  udevcontrol log_priority=info