Re: RFC 4833 / TimeZone by DHCP
On Wed, 2007-12-05 at 20:26 -0600, Federico Mena Quintero wrote: On Mon, 2007-12-03 at 19:08 -0500, Dan Williams wrote: Or the international clock listens and makes the change since it knows how to do that. Exactly; that's the ideal case. I want the model to be pull _from_ NetworkManager provided information, not have NM push stuff out. I'm a bit late into the conversation. How would this work? 1. Clock listens for network went up/down 2. When the network goes up, the clock asks NM for gimme the DHCP data 3. Clock sets the timezone. What happens if you don't have a clock applet? :) Should NM just have a magic script to set the timezone? NM itself shouldn't do that, something else (NetworkManagerDispatcher or another tool) should be listening to the updates and grabbing the data. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Thu, 2007-12-06 at 06:09 -0500, Dan Williams wrote: On Wed, 2007-12-05 at 20:26 -0600, Federico Mena Quintero wrote: Should NM just have a magic script to set the timezone? NM itself shouldn't do that, something else (NetworkManagerDispatcher or another tool) should be listening to the updates and grabbing the data. Ah, OK. I *thinK* the clock already watches for changes in /etc/localtime anyway. Federico ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Mon, 2007-12-03 at 19:08 -0500, Dan Williams wrote: Or the international clock listens and makes the change since it knows how to do that. Exactly; that's the ideal case. I want the model to be pull _from_ NetworkManager provided information, not have NM push stuff out. I'm a bit late into the conversation. How would this work? 1. Clock listens for network went up/down 2. When the network goes up, the clock asks NM for gimme the DHCP data 3. Clock sets the timezone. What happens if you don't have a clock applet? :) Should NM just have a magic script to set the timezone? Federico ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Tue, 2007-12-04 at 08:46 +0100, Dominique Leuenberger wrote: Hello On 12/4/2007 at 2:08 AM, Dan Williams [EMAIL PROTECTED] wrote: Or the international clock listens and makes the change since it knows how to do that. Exactly; that's the ideal case. I want the model to be pull _from_ NetworkManager provided information, not have NM push stuff out. Well, that sounds actually like a very ideal cae. Is there somewhere already documented how any application can pull any information from NM? Is this interface ready? If so, I could start getting in touch with the 'International Clock' team for an implementation from this side. No, the interface isn't defined yet. Comments and suggestions welcome... I currently envision that it would be a D-Bus interface of any currently active Connection object. However, Connection objects aren't represented as first-class objects in NM yet, which we may wish to do for this and other reasons. Dan If the interface in NM is not defined yet, there is of course only little point in this. They could not implement anything working. Thank you for your consideration; I like the way it's approached and I see a solution for the problem on the horizon. Dominique TMF is a global management and accounting outsourcing firm with 77 offices in 60 countries and over 2,000 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RFC 4833 / TimeZone by DHCP
Hello, after asking over at openSUSE wether it would be possible to support RFC4833 (Timezone settings distributed by DHCP), I was told it might be better to ask this here. Background: As an international traveling user (mostly inside our company) I would like very much to have the ability to have an accurate, local time on my system wherever I am. RFC 4833 aims directly at this and allows network administrators to push out via DHCP the current time zone (which can easily configured). Would it be possible to implement this into our NM? Thank you very much for considering it. Dominique Leuenberger TMF is a global management and accounting outsourcing firm with 77 offices in 60 countries and over 2,000 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Dec 3, 2007 11:06 AM, Dominique Leuenberger [EMAIL PROTECTED] wrote: As an international traveling user (mostly inside our company) I would like very much to have the ability to have an accurate, local time on my system wherever I am. RFC 4833 aims directly at this and allows network administrators to push out via DHCP the current time zone (which can easily configured). Would it be possible to implement this into our NM? NM just gained the ability to support static routes from DHCP (http://mail.gnome.org/archives/networkmanager-list/2007-November/msg00173.html), if anyone's interested in adding time zone support, using that patch as a template should make it pretty easy. The only tricky part may be the actual setting of the time zone in such a way that it would work on all distros. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Mon, 2007-12-03 at 16:07 +0200, Tambet Ingo wrote: On Dec 3, 2007 11:06 AM, Dominique Leuenberger [EMAIL PROTECTED] wrote: As an international traveling user (mostly inside our company) I would like very much to have the ability to have an accurate, local time on my system wherever I am. RFC 4833 aims directly at this and allows network administrators to push out via DHCP the current time zone (which can easily configured). Would it be possible to implement this into our NM? NM just gained the ability to support static routes from DHCP (http://mail.gnome.org/archives/networkmanager-list/2007-November/msg00173.html), if anyone's interested in adding time zone support, using that patch as a template should make it pretty easy. The only tricky part may be the actual setting of the time zone in such a way that it would work on all distros. Although, I don't want to stuff every option for things like this into NM. Since obsoleting dhcdbd, what I'd like to see is this: a) NM exports a D-Bus interface (the most likely object for this is the Connection that just got activated) that allows things to query the DHCP information. This interface sends out signals when the DHCP information is cleared/updated/etc b) NetworkManagerDispatcher listens for these signals and executes scripts to do things with them, or something like that. I think it makes sense for static routes and such things to be handled by NM, but we quickly start getting to things that I don't think _should_ be handled by NM itself. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Mon, 2007-12-03 at 09:38 -0500, Dan Williams wrote: On Mon, 2007-12-03 at 16:07 +0200, Tambet Ingo wrote: On Dec 3, 2007 11:06 AM, Dominique Leuenberger [EMAIL PROTECTED] wrote: As an international traveling user (mostly inside our company) I would like very much to have the ability to have an accurate, local time on my system wherever I am. RFC 4833 aims directly at this and allows network administrators to push out via DHCP the current time zone (which can easily configured). Would it be possible to implement this into our NM? NM just gained the ability to support static routes from DHCP (http://mail.gnome.org/archives/networkmanager-list/2007-November/msg00173.html), if anyone's interested in adding time zone support, using that patch as a template should make it pretty easy. The only tricky part may be the actual setting of the time zone in such a way that it would work on all distros. Although, I don't want to stuff every option for things like this into NM. Since obsoleting dhcdbd, what I'd like to see is this: a) NM exports a D-Bus interface (the most likely object for this is the Connection that just got activated) that allows things to query the DHCP information. This interface sends out signals when the DHCP information is cleared/updated/etc b) NetworkManagerDispatcher listens for these signals and executes scripts to do things with them, or something like that. Or the international clock listens and makes the change since it knows how to do that. -JP -- JP Rosevear [EMAIL PROTECTED] Novell, Inc. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
On Mon, 2007-12-03 at 18:23 -0500, JP Rosevear wrote: On Mon, 2007-12-03 at 09:38 -0500, Dan Williams wrote: On Mon, 2007-12-03 at 16:07 +0200, Tambet Ingo wrote: On Dec 3, 2007 11:06 AM, Dominique Leuenberger [EMAIL PROTECTED] wrote: As an international traveling user (mostly inside our company) I would like very much to have the ability to have an accurate, local time on my system wherever I am. RFC 4833 aims directly at this and allows network administrators to push out via DHCP the current time zone (which can easily configured). Would it be possible to implement this into our NM? NM just gained the ability to support static routes from DHCP (http://mail.gnome.org/archives/networkmanager-list/2007-November/msg00173.html), if anyone's interested in adding time zone support, using that patch as a template should make it pretty easy. The only tricky part may be the actual setting of the time zone in such a way that it would work on all distros. Although, I don't want to stuff every option for things like this into NM. Since obsoleting dhcdbd, what I'd like to see is this: a) NM exports a D-Bus interface (the most likely object for this is the Connection that just got activated) that allows things to query the DHCP information. This interface sends out signals when the DHCP information is cleared/updated/etc b) NetworkManagerDispatcher listens for these signals and executes scripts to do things with them, or something like that. Or the international clock listens and makes the change since it knows how to do that. Exactly; that's the ideal case. I want the model to be pull _from_ NetworkManager provided information, not have NM push stuff out. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: RFC 4833 / TimeZone by DHCP
Hello On 12/4/2007 at 2:08 AM, Dan Williams [EMAIL PROTECTED] wrote: Or the international clock listens and makes the change since it knows how to do that. Exactly; that's the ideal case. I want the model to be pull _from_ NetworkManager provided information, not have NM push stuff out. Well, that sounds actually like a very ideal cae. Is there somewhere already documented how any application can pull any information from NM? Is this interface ready? If so, I could start getting in touch with the 'International Clock' team for an implementation from this side. If the interface in NM is not defined yet, there is of course only little point in this. They could not implement anything working. Thank you for your consideration; I like the way it's approached and I see a solution for the problem on the horizon. Dominique TMF is a global management and accounting outsourcing firm with 77 offices in 60 countries and over 2,000 professionals (2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
