Bug 154034

Summary: slightly disturbing message at boot time from kill(1)
Product: [openSUSE] SUSE Linux 10.1 Reporter: Jon Nelson <jnelson-suse>
Component: BasesystemAssignee: Hannes Reinecke <hare>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 5   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: invalid use of 'kill(1)'

Description Jon Nelson 2006-02-28 04:29:07 UTC
It's very hard to describe, I included a screenshot.
Comment 1 Jon Nelson 2006-02-28 04:29:48 UTC
Created attachment 70567 [details]
invalid use of 'kill(1)'
Comment 2 Michael Gross 2006-02-28 12:22:56 UTC
Does this happen in the first or second stage of the installation, in the rescue system or in the installed system?
Comment 3 Jon Nelson 2006-02-28 15:23:48 UTC
This happens every time I boot after installation.
Comment 4 Michael Gross 2006-02-28 15:54:07 UTC
Please attach your /etc/fstab here, this seems to happen while the filesystems are being mounted however I don't know why this script would make use of kill.
Comment 5 Jon Nelson 2006-02-28 16:14:54 UTC
Well, it's /before/ the INIT so I don't think it has to do with filesystems - this looks like a bug in the initrd. Although not shown, the filesystems aren't examined until quite a bit later (although you can see swap being added here).

I *think* it's near lines 2616-2620 from mkinitrd:

        |# kill udevd, we will run the one from the real root
        |kill $(pidof udevd)
        |
        |# kill iscsid, will be restarted from the real root
        |kill -KILL $(pidof iscsid)

I'll try to get at fstab tonight (can't right now).
Comment 6 Michael Gross 2006-02-28 16:17:36 UTC
Allright, this is an initrd issue. Reassigning to the kernel maintainers.
Comment 7 Lars Marowsky-Bree 2006-02-28 16:23:55 UTC
mkinitrd -> not kernel, but Hannes.
Comment 8 Hannes Reinecke 2006-03-01 12:24:16 UTC
And is already fixed.

*** This bug has been marked as a duplicate of 153374 ***