Description of problem: When I run dhcp6s it stuck in a loop.It should run as a deamon. And return to a shell. This bug block tahi dhcpv6 test case. Version-Release number of selected component (if applicable): dhcpv6-1.0.10-7.el5 How reproducible: Always Steps to Reproduce: 1.vi /tmp/dhcp6s.conf interface eth0 { #server-preference 255; renew-time 5000; rebind-time 8000; prefer-life-time 10000; valid-life-time 10000; #allow rapid-commit; option dns_servers 3ffe:501:ffff:100:210:18ff:fe32:56e2 redhat.com; #option dns_servers 3ffe:501:ffff:100::10; link AAA { pool{ range 3ffe:501:ffff:101::10 to 3ffe:501:ffff:101::11/64; prefix 3ffe:501:ffff:101::/48; }; }; host TN { duid 00:01:00:01:00:04:93:e0:00:00:00:00:a2:a2; }; }; 2.run command #dhcp6s -dDf -c /tmp/dhcp6s.conf eth0(your interface name) Actual results: Jul/23/2008 01:16:22 extracted an existing DUID from /var/lib/dhcpv6/dhcp6s_duid: 00:01:00:01:10:18:d0:6a:02:00:00:00:03:00 Jul/23/2008 01:16:22 found an interface eth0 harware 00:10:18:32:56:e2 Jul/23/2008 01:16:22 saved generated DUID to /var/lib/dhcpv6/dhcp6s_duid Jul/23/2008 01:16:22 set timer for syncing file ... Jul/23/2008 01:16:22 add domain name redhat.com Jul/23/2008 01:16:22 configure duid is 00:01:00:01:00:04:93:e0:00:00:00:00:a2:a2 Jul/23/2008 01:16:22 interface definition for eth0 is ok It always stop here. Expected results: should return a shell and continue run dhcp6s in backend. Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
(In reply to comment #0) > #dhcp6s -dDf -c /tmp/dhcp6s.conf eth0(your interface name) The -f switch for dhcp6s causes the program to run in the foreground. If you want it to run as a background process, do not specify the -f switch on the command line.
oh good. After I change the command.The tahi test case can be run in debug mode now. And any question When Can I get the detail debug log /var/log/message ? I only can see very simple message in /var/log/message.