Re: [gentoo-user] Re: udev and init.d. Should it be running now?

[Dale <rdalek1967@gmail.com>]

walt wrote:
> On 09/10/2009 03:43 PM, Dale wrote:
>> Jonathan Callen (ABCD) wrote:
>>> Dale wrote:
>>>> Hi folks,
>>>
>>>> I was browsing around and noticed that I now have a udev in
>>>> /etc/init.d/.  I checked, it is not running but udevd is not running
>>>> either.  See below:
>>>
>>>>> root@smoker / # /etc/init.d/udev status
>>>>>   * status:  stopped
>>>>> root@smoker / #
>>>>> root@smoker / # ps aux | grep udev
>>>>> root     30451  0.0  0.0   1888   504 pts/0    R+   16:04   0:00 grep
>>>>> --colour=auto udev
>>>>> root@smoker / #
>
>>>> Also, keep in mind, everything works fine.  I just don't want to
>>>> add it
>>>> to boot or default runlevels and then break something.
>>>
>>> In baselayout-1, udev is started directly by baselayout itself, outside
>>> of any init scripts.  In baselayout-2/openrc, an initscript is
>>> needed to
>>> start udev.  If you actually read the script, you may notice that the
>>> script will immediately fail if you attempt to run it on a baselayout-1
>>> system, as it isn't needed...
>>
>> ...Anyway, I used ps and less to list those processes and noticed
>> that udev was not running.  It used to be running in the past.
>
> I was surprised to read Jonathan's post, but I see he's right.  On my
> x86 machine the status of udev is "stopped" and on ~amd64 it's "started".
>
> But both machines show that /sbin/udevd is indeed running, so I can see
> why you are uneasy about your status quo.
>
> Have you tried running /sbin/udevd --daemon from a command prompt? When
> I try it I get a message that udevd is already running.
>

OK.  Now I feel better.  I used your command and now it is running.  I
hope it will run when I reboot.  o_O

root@smoker / # /sbin/udevd --daemon
root@smoker / # ps aux | grep udev
root      2595  0.0  0.0   2204   780 ?        S<s  20:23   0:00
/sbin/udevd --daemon
root      2599  0.0  0.0   1888   512 pts/0    S+   20:23   0:00 grep
--colour=auto udev
root@smoker / #

At least I know udev works now.  I was hoping that something hadn't been
broken and I just didn't notice it. 

Thanks much for the info.  I know how to start it if it is not running
at least.

Dale

:-)  :-)