Re: [gentoo-user] Re: udev and init.d. Should it be running now?
Dale wrote: Philip Webb wrote: 090910 Dale wrote: I noticed I now have a udev in /etc/init.d/. I checked, it is not running but udevd is not running either: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0 R+ 16:04 0:00 grep --colour=auto udev Using Baselayout 1.12.11.1 Udev 141 , I get : root:508 default ps aux | grep udev root 659 0.0 0.0 12524 936 ? Ss Sep10 0:00 /sbin/udevd --daemon So it should be running all the time then but for some reason it wasn't on mine. Hmmm. I'm going to reboot sometime soon and I'll check to see if it is running then. I hope this was just a fluke of some kind. Thanks for all the help. I'll report back if it doesn't start as it should. Dale :-) :-) I rebooted, into a new kernel I made a few days ago, and udev is running without me having to start it or anything. I dunno what the heck happened. It is running now so I guess it was a fluke of some kind. Thanks for the help. I'm off to research building a Phenom II x4 puter. o_O Dale :-) :-)
[gentoo-user] Re: udev and init.d. Should it be running now?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0R+ 16:04 0:00 grep --colour=auto udev r...@smoker / # This is the baselayout that is installed: [I--] [ ] sys-apps/baselayout-1.12.11.1 I seem to recall that baselayout 2 is going to be a service thing but since I am on baselayout 1, should this be running? It seems to belong to the udev package tho according to this: r...@smoker / # equery belongs /etc/init.d/udev [ Searching for file(s) /etc/init.d/udev in *... ] sys-fs/udev-141 (/etc/init.d/udev) r...@smoker / # You can see from that what udev version is installed too. I also checked the elogs and I see no mention of it being changed to a service or that it needs to be added to a runlevel. Also, keep in mind, everything works fine. I just don't want to add it to boot or default runlevels and then break something. Thanks for any advice. I searched the forums and udev on g.o but didn't see anything relevant. Dale :-) :-) 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. If/when you upgrade to baselayout-2/openrc, it will automatically be added to the boot runlevel, but only if baselayout-1 had been previously installed. In short, don't worry about it. :) (this didn't appear to send the first time, so resending...) - -- Jonathan Callen (ABCD) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqpeCgACgkQOypDUo0oQOppywCfa3+jnwddXZfocNqvDeWbbjGC 3UAAoL7b9ElKq+72QpFwtrW/hpSWVUOD =3KGk -END PGP SIGNATURE-
Re: [gentoo-user] Re: udev and init.d. Should it be running now?
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: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0R+ 16:04 0:00 grep --colour=auto udev r...@smoker / # This is the baselayout that is installed: [I--] [ ] sys-apps/baselayout-1.12.11.1 I seem to recall that baselayout 2 is going to be a service thing but since I am on baselayout 1, should this be running? It seems to belong to the udev package tho according to this: r...@smoker / # equery belongs /etc/init.d/udev [ Searching for file(s) /etc/init.d/udev in *... ] sys-fs/udev-141 (/etc/init.d/udev) r...@smoker / # You can see from that what udev version is installed too. I also checked the elogs and I see no mention of it being changed to a service or that it needs to be added to a runlevel. Also, keep in mind, everything works fine. I just don't want to add it to boot or default runlevels and then break something. Thanks for any advice. I searched the forums and udev on g.o but didn't see anything relevant. Dale :-) :-) 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. If/when you upgrade to baselayout-2/openrc, it will automatically be added to the boot runlevel, but only if baselayout-1 had been previously installed. In short, don't worry about it. :) (this didn't appear to send the first time, so resending...) What you say makes sense but why is udev not running on my system anymore? I noticed this mostly because I went to single user, KDE seemed to have a few processes that didn't want to die when I logged out. 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. That got me to looking and that is when I found the init script. Even after logging back into KDE, udev was still not running. I'm sort of concerned that something is not quite right. I haven't rebooted in a week or two either. Ideas? Thoughts? Dale :-) :-)
[gentoo-user] Re: udev and init.d. Should it be running now?
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: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0R+ 16:04 0:00 grep --colour=auto udev r...@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.
Re: [gentoo-user] Re: udev and init.d. Should it be running now?
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: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0R+ 16:04 0:00 grep --colour=auto udev r...@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 r...@smoker / # /sbin/udevd --daemon r...@smoker / # ps aux | grep udev root 2595 0.0 0.0 2204 780 ?Ss 20:23 0:00 /sbin/udevd --daemon root 2599 0.0 0.0 1888 512 pts/0S+ 20:23 0:00 grep --colour=auto udev r...@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 :-) :-)
Re: [gentoo-user] Re: udev and init.d. Should it be running now?
090910 Dale wrote: I noticed I now have a udev in /etc/init.d/. I checked, it is not running but udevd is not running either: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0 R+ 16:04 0:00 grep --colour=auto udev Using Baselayout 1.12.11.1 Udev 141 , I get : root:508 default ps aux | grep udev root 659 0.0 0.0 12524 936 ? Ss Sep10 0:00 /sbin/udevd --daemon -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Re: udev and init.d. Should it be running now?
Philip Webb wrote: 090910 Dale wrote: I noticed I now have a udev in /etc/init.d/. I checked, it is not running but udevd is not running either: r...@smoker / # /etc/init.d/udev status * status: stopped r...@smoker / # ps aux | grep udev root 30451 0.0 0.0 1888 504 pts/0 R+ 16:04 0:00 grep --colour=auto udev Using Baselayout 1.12.11.1 Udev 141 , I get : root:508 default ps aux | grep udev root 659 0.0 0.0 12524 936 ? Ss Sep10 0:00 /sbin/udevd --daemon So it should be running all the time then but for some reason it wasn't on mine. Hmmm. I'm going to reboot sometime soon and I'll check to see if it is running then. I hope this was just a fluke of some kind. Thanks for all the help. I'll report back if it doesn't start as it should. Dale :-) :-)
