On Wed, Mar 06, 2013 at 01:03:49PM +0200, Patrik Flykt wrote:
> Let's go with your patch as it solves a problem. Applied!
Thanks!
-Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com
signature.asc
Description: Digital signature
_
On Mon, 2013-03-04 at 09:48 -0500, Forest Bond wrote:
> My patch fixes the initial wispr check on service reconfiguration,
> which is
> fragile and depends on the service properties being set in a
> particular order.
> This prevents a service from properly entering online state. It's a
> bug.
>
>
Hi Patrik,
On Fri, Jan 04, 2013 at 12:33:36PM +0200, Patrik Flykt wrote:
> On Wed, 2012-12-05 at 16:44 -0500, Forest Bond wrote:
> > From: Forest Bond
> >
> > This is needed to make a service go online in the case where it was
> > already connected and then manual IPv4 & nameservers settings are
Hi,
On Wed, 2012-12-05 at 16:44 -0500, Forest Bond wrote:
> From: Forest Bond
>
> This is needed to make a service go online in the case where it was
> already connected and then manual IPv4 & nameservers settings are
> applied. In that case, wispr is restarted with the new IP settings
Hi,
Anyone have a chance to take a look at this one?
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com
On Wed, Dec 05, 2012 at 04:44:27PM -0500, Forest Bond wrote:
> From: Forest Bond
>
> This is needed to make a service go online in the case where it wa
From: Forest Bond
This is needed to make a service go online in the case where it was
already connected and then manual IPv4 & nameservers settings are
applied. In that case, wispr is restarted with the new IP settings, but
the nameservers have not been set yet, so the wispr test fails and the
s
