Description of problem: The dhcpv6_client RPM is missing the init from the upstream package. The spec does not include the file. Makefile does not install file. Version-Release number of selected component (if applicable): dhcpv6_client-0.10-14_EL4 dhcpv6_client-0.10-16.1 (fc5 as well) How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: /etc/init.d/dhcp6c exists Additional info: Patch for Makefile.in and dhcpv6.spec attached
Created attachment 126955 [details] Makefile.in patch to install DHCPv6 client init.d file
Created attachment 126956 [details] Patch for dhcpv6.spec
Created attachment 126958 [details] patch for /etc/rc.d/init.d/dhcp6c
Actually, both in FC-{4,5,6} and RHEL-4, we tried to follow the same conventions as used by dhclient: dhcp6c does NOT have its own initscript, but is started by an 'ifup' IFF these /etc/sysconfig/network{,-scripts/ifcfg-eth*} variables are set: NETWORKING_IPV6=yes DHCPV6C=yes This is documented in /usr/share/doc/initscripts-*/sysconfig.txt: " IPv6-only option to enable DHCPv6 client: DHCPV6C=yes|no This will enable the DHCPv6 client, dhcp6c, to be run for the interface. See man dhcp6c(8) and dhcp6c.conf(5). ". I don't think it would be a good idea to give dhcp6c its own initscript, as this would REQUIRE users to set up /etc/dhcp6c.conf with 'interface ...{...}' definitions, and would result in more user confusion. With the sysconfig variable settings, users do not have to set up a dhcp6c config file, since dhcp6c can be given the explicit 'dhcp6c $DEVICE' argument automatically.