Bug 657651

Summary: udev-164-5.fc15 whines during an update
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: harald, jonathan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-06 09:57:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2010-11-27 01:05:22 UTC
Description of problem:

Updating udev in rawhide effects the following:
....
  Updating       : udev-164-5.fc15.x86_64                                   6/161 
/var/tmp/rpm-tmp.B4KK0z: line 14: kill: (373) - No such process
.....

That line number strongly suggest that the following loop from preinstall scriptlet is responsible:

    while [ -n "$pid" ]; do
            for p in $pid; do
                    kill $hard $p;
            done
            pid=$(/sbin/pidof -c udevd)
            hard="-9"
    done

Smells like a race with /sbin/pidof still seeing udevd after the first 'kill' because udevd takes some time to cleanly terminate.

If we do not care then why not to do '... done >/dev/null 2>&1' and shut this up? Another option is to wait a bit before the "pidof" check.

Version-Release number of selected component (if applicable):
udev-164-5.fc15

Comment 1 Michal Jaegermann 2010-12-03 18:49:29 UTC
The same "No such process" happened when updating to udev-153-5.fc13.x86_64, with line 17 this time, on one machine but not on another one. Again, /sbin/pidof runs too quickly after kill.