icinga 1.3.1 and 1.4.0 for lucid / natty
Hi, I'm not sure if it's the right place to ask, but I was a bit confused by the bug tracker, demanding different versions for different releases. Even more, I am not sure who takes care of porting the Nagios / Icinga packages from Debian to Ubuntu. So please excuse my n00bish question on how to get at least Icinga 1.3.1 (bugfixed 1.3.0 release) into the stable tree (maybe as backport) into lucid and natty? And even - when official Debian pkg are there in backports, expected soon - bring Icinga 1.4.0 from yesterday's release into the experimental or testing tree. Thoughts/Hints? Thanks, Michael -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 mobile: +43 664 60277 14359 fax:+43 1 4277 14338 web:http://www.univie.ac.at/zid http://www.aco.net Icinga Core& IDOUtils Developer http://www.icinga.org -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Disconnect via NetworkManager should send DHCPRELEASE when applicable
On Wed, May 11, 2011 at 9:10 AM, Thomas Novin wrote: > Hello > > I think NetworkManager should send a DHCPRELEASE when the user chooses > disconnect on a DHCP-connection. > > This is important when using a service that only allows one IP, then the > MAC/IP-combo is locked for whatever the DHCP lease-time is. Sending a > DHCPRELEASE frees up the lease making the service available for another > computer. > > Any reason why not to do this? Should I file a Launchpad bug? Hi Thomas, I'm not sure if there is a specific reason. However, seems to me like this would need careful consideration, given that what we usually want is for NM to retain IP addresses at least on wired, if it gets shutdown (e.g. the daemon is stopped or killed, etc.). Then you get into the question of how to deal with differenciating a user-initiatied *disconnect* rather than a shutdown of the daemon. You'll also get into the cases where you really want to disconnect for whatever reason, but want/need to retain your IP if possible. I think this is the most likely use case. I think this would probably be better served in your case by a dispatcher script: you can drop files in /etc/NetworkManager/dispatcher.d to have them run on various events; just take a look at 01ifupdown for inspiration; you should easily be able to do something like 'dhclient -r' from there to achieve the same thing. Otherwise, I guess you might want to ask on the NetworkManager list, which would be better suited for this kind of targetted question about this project. Regards, Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu...@gmail.com 4096R/EE018C93 1967 8F7D 03A1 8F38 732E FF82 C126 33E1 EE01 8C93 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Disconnect via NetworkManager should send DHCPRELEASE when applicable
Hello I think NetworkManager should send a DHCPRELEASE when the user chooses disconnect on a DHCP-connection. This is important when using a service that only allows one IP, then the MAC/IP-combo is locked for whatever the DHCP lease-time is. Sending a DHCPRELEASE frees up the lease making the service available for another computer. Any reason why not to do this? Should I file a Launchpad bug? Rgds//Thomas -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
