Re: problem with dhclient after update to FreeBSD-8.3
On 05/05/2012 19:30, Carmel wrote: I just updated my system to FreeBSD 8.3-STABLE #0 from version 8.2. I was getting warning messages regarding webcamd at boot-up; however, I got them fixed (I think) I loaded: cuse4bsd_load=YES in the loader.conf file and placed: webcamd_enable=YES in the rc.conf file. I had never used it before; however, I am assuming that the 8.3 version somehow requires it. What's happening is that 8.3 has introduced more comprehensive support for a wider range of USB devices. It's just picking up on the presence of a webcam now and suggesting software that could manage it. You don't need to enable the webcam at all: the kernel will recognise it as a webcam from its built-in identifying codes, but unless you enable some software to deal with it, it won't be able to do anything. This usually shows up with USB ethernet devices suddenly appearing and cluttering up ifconfig(8) output -- unlike webcams, ethernet interfaces generally do have kernel level support automatically enabled. devd will try and run dhclient on the interface to configure it, which I guess is where your extra dhclent invocation is coming from. It is possible to turn this behaviour off by adding something like: hint.usb.0.disabled=1 into /boot/loader.conf but this is using a sledgehammer to crack a nut, as that turns off that usb bus entirely. (Warning: This may well have deleterious effects on your ability to use a keyboard or mouse with the system: use cautiously. Also, change that '0' to the appropriate bus number if you need to) dhclient is listed as starting at the beginning of the log and again at the end. I never had this happen when using FreeBSD-8.2. I am still confused as to why devd wants to start webcamd devd only wants to start webcamd because you've installed the webcamd software including /usr/local/etc/devd/webcamd.conf If you pkg_delete the webcamd stuff and then restart devd, it won't try starting up webcamd any more. All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 6 May 2012, Matthew Seaman wrote: On 05/05/2012 19:30, Carmel wrote: All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 may be relevant. It's on 9-stable, I haven't compared with 8.3. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 6 May 2012 04:25:52 -0600 (MDT) Warren Block articulated: On Sun, 6 May 2012, Matthew Seaman wrote: On 05/05/2012 19:30, Carmel wrote: All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 may be relevant. It's on 9-stable, I haven't compared with 8.3. Warren, I posted an addendum to that PR to indicate that the behavior is also occurring on 8.3 systems as well. Do you think it would be prudent to open a new PR with my info since it concerns FreeBSD-8.3 STABLE and not the 9.0 branch? I was also wondering if anyone other than myself is seeing this phenomenon on the 8.3 version. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 06 May 2012 10:48:31 +0100 Matthew Seaman articulated: On 05/05/2012 19:30, Carmel wrote: I just updated my system to FreeBSD 8.3-STABLE #0 from version 8.2. I was getting warning messages regarding webcamd at boot-up; however, I got them fixed (I think) I loaded: cuse4bsd_load=YES in the loader.conf file and placed: webcamd_enable=YES in the rc.conf file. I had never used it before; however, I am assuming that the 8.3 version somehow requires it. What's happening is that 8.3 has introduced more comprehensive support for a wider range of USB devices. It's just picking up on the presence of a webcam now and suggesting software that could manage it. You don't need to enable the webcam at all: the kernel will recognise it as a webcam from its built-in identifying codes, but unless you enable some software to deal with it, it won't be able to do anything. While that may well be true, it does clutter up the boot-up process with a lot of sinister if only benign looking warning messages. There should be a way to silence them or at least make the warning message less sinister looking. Something like: webcamd present but not enabled like is done for other devices. This usually shows up with USB ethernet devices suddenly appearing and cluttering up ifconfig(8) output -- unlike webcams, ethernet interfaces generally do have kernel level support automatically enabled. devd will try and run dhclient on the interface to configure it, which I guess is where your extra dhclent invocation is coming from. It is possible to turn this behaviour off by adding something like: hint.usb.0.disabled=1 into /boot/loader.conf but this is using a sledgehammer to crack a nut, as that turns off that usb bus entirely. (Warning: This may well have deleterious effects on your ability to use a keyboard or mouse with the system: use cautiously. Also, change that '0' to the appropriate bus number if you need to) I think I will skip the sledgehammer technique for now. Thanks for the suggestion though. :) dhclient is listed as starting at the beginning of the log and again at the end. I never had this happen when using FreeBSD-8.2. I am still confused as to why devd wants to start webcamd devd only wants to start webcamd because you've installed the webcamd software including /usr/local/etc/devd/webcamd.conf If you pkg_delete the webcamd stuff and then restart devd, it won't try starting up webcamd any more. I don't think removing it is really an option: pkg_info -R webcamd-3.5.0.2 Information for webcamd-3.5.0.2: Required by: gstreamer-plugins-all-1.3.0.10.1_12 gstreamer-plugins-v4l2-0.10.30,3 kde-4.7.4_1 kde-workspace-4.7.4_1 kdeartwork-4.7.4_1 kdenetwork-4.7.4_2 kdeplasma-addons-4.7.4_1 kdetoys-4.7.4_1 kdeutils-4.7.4_2 phonon-gstreamer-4.5.1 qt4-4.7.4 qt4-qtconfig-4.7.4 Interestingly enough, I never had webcamd initiated in the /etc/rc.conf file and never received a warning message about it having to be initialized until the update to FreeBSD-8.3. I am not sure if this should be considered a BUG or what. It doesn't appear that any of the software that requires it to be installed also require it to be running at boot-up. I don't even know who, if anyone, I should report this behavior to. All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. There does appear to be a PR listed against this behavior as noted in Warren's post on this thread. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 Thanks for your assistance Matthew. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
problem with dhclient after update to FreeBSD-8.3
I just updated my system to FreeBSD 8.3-STABLE #0 from version 8.2. I was getting warning messages regarding webcamd at boot-up; however, I got them fixed (I think) I loaded: cuse4bsd_load=YES in the loader.conf file and placed: webcamd_enable=YES in the rc.conf file. I had never used it before; however, I am assuming that the 8.3 version somehow requires it. I am still receiving an error message regarding dhclient. This is an snippet of the screen logging at boot-up: nfe0: link state changed to DOWN Starting dhclient. nfe0: no link nfe0: link state changed to UP got link DHCPREQUEST on nfe0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.101 -- renewal in 43200 seconds. Starting Network: lo0 nfe0. lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 nd6 options=3PERFORMNUD,ACCEPT_RTADV nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=82008VLAN_MTU,WOL_MAGIC,LINKSTATE ether 00:19:21:5d:34:de inet 192.168.1.101 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,t xpause) status: active add net :::0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1nfe0: link state changed to DOWN Starting devd. Starting webcamd. Attached ugen1.3[0] to cuse unit -1 Starting webcamd. Attached ugen1.3[1] to cuse unit -1 Starting webcamd. Attached ugen1.3[2] to cuse unit -1 Starting ums0 moused. Starting webcamd. Attached ugen1.4[0] to cuse unit -1 Starting webcamd. Attached ugen1.4[1] to cuse unit -1 dhclient already running? (pid=435). dhclient is listed as starting at the beginning of the log and again at the end. I never had this happen when using FreeBSD-8.2. I am still confused as to why devd wants to start webcamd All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
