Pierre Labastie wrote: > Hi, > > I eventually decided to study slightly more dhcpcd. > A few switch may be suppressed, since they are the defaults. > > Also, the > installation of 50-dhcpcd-compat is not needed anymore, since > dhcpcd creates a (binary) lease information file in /var/run (which is > linked to /run), and that information may be dumped with the > command: > dhcpcd --dumplease <interface> > > The only reason to install the hook would be if some package > needed a textual lease info file. I doubt there is any. > > Another reason could be to keep the lease across > reboots, in case the dhcp server does not answer. > But the file is not kept anyway, since /run is a tmpfs, > unless we put the lease in some permanent place > like /var/lib. So the sed before the installation of > 50-dhcpcd-compat should not be done anyway. > OTOH, we should then instruct dhcpcd to > use that file, which does not seem possible without > writing a script. > > Another way to have the lease persistent across reboot > is to specify --rundir=/var/lib (or anything not tmpfs). > This might make it be easier to reuse a lease.
The place to put temporary files that persist across boots is /var/tmp. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page