Bug 4692 - 2_b1: udev-post: "unknown type --type=failed" start/reload message
Summary: 2_b1: udev-post: "unknown type --type=failed" start/reload message
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-25 12:44 CET by Bit Twister
Modified: 2012-02-26 23:11 CET (History)
8 users (show)

See Also:
Source RPM: udev-181-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2012-02-25 12:44:53 CET
Description of problem:

When /etc/rc.d/init.d/udev-post starts/reloads, it prints 
unknown type --type=failed

Line 28 should be changed to something like
echo Starting udev-post

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


How reproducible: Always


Steps to Reproduce:
1. grep -i fail /var/log/messages
2.
3.
Comment 1 Bit Twister 2012-02-25 13:01:17 CET
Better suggestion, make it
echo ${1}ing udev-post
Comment 2 Dave Hodgins 2012-02-25 22:43:44 CET
According to
http://udev.sourcearchive.com/documentation/173-0ubuntu1/udevadm-trigger_8c_source.html
udevadm trigger --type=failed
has been deprecated.  Looks like it's finally been removed.

CC: (none) => davidwhodgins

Comment 3 Manuel Hiebel 2012-02-26 22:00:29 CET
Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

CC: (none) => anssi.hannula, dmorganec, mageia, mageia, pterjan, thierry.vignaud, tmb

Comment 4 Colin Guthrie 2012-02-26 22:17:13 CET
Hmm, yeah I think the whole udev-post script can probably be killed now...
Comment 5 Colin Guthrie 2012-02-26 22:40:03 CET
*** Bug 4695 has been marked as a duplicate of this bug. ***
Comment 6 Colin Guthrie 2012-02-26 23:11:48 CET
OK, I've dropped the udev-post script.

For reference, I'm not sure that what it did regarding copying the temporary rules to persistent rules in /etc/udev/rules.d/ is not replaced with new code, but I cannot find any code in udev that would write rules in this location (it would now-adays be /run/udev/ rather than /dev/.udev/ anyway).

So with this in mind, I've just removed it. This might also related to some other reports recently about persistent-net.rules files (included in dracut's network module now) which may make including such files no longer appropriate.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.