> Interesting, yes I'd say that rules out dhcdbd. Be nice to find out what > the problem was, and maybe how they now do it.
The commit i posted to shows they call dhclient directly now (i think, its encrusted in a lot of scary glib foo). Actually, poking a bit more.. they use the -sf param of dhclient to have it run a callback when it is done stuff. By default, this is the /sbin/dhclient-script script. When the script is called, $reason is set to an event like TIMEOUT, BOUND, RENEW, etc. Other useful stuff is available in other variables.. The results of the DHCP event is by default mapped to ifconfig actions. The NetworkManager version of this script is here: http://svn.gnome.org/viewvc/NetworkManager/trunk/callouts/nm-dhcp-client-action.c?view=markup It just pushes all those evn variables into a dictionary and lobs it at the NetworkManager dbus iface. NetworkManager also tells dhclient to use a custom lease file and a custom pid file. All very fancy, but we can just get away with looking for something like this in a python script that sits between HAL and hal-dccm: DHCPACK from 192.168.0.1 bound to 192.168.0.151 -- renewal in 128851 seconds. > While I think this could still be a pain, I can't see any problem with > going with it to start with and see how it goes. > > This is a hal solution of course. Odccm needs a different solution until > everyone is happy with hal. As a short term solution in odccm I'd say > calling dhclient is the easy answer, except for parsing its output using > C, which would probably result in a dependency on a regex lib. > > Dont know. > > Mark I don't know that we even have to fix it for odccm. hal-dccm is meant to be the plug and play version of odccm, right? So why put plug and play type fixes in to odccm. Uses can manually dhclient as they do now :P Most users are lucky and don't even need this step, and if it becomes a problem we could always provide a script that ran dhclient then odccm for the user if it was so desired. John ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
