On Wed, Feb 21, 2007 at 04:31:42PM +0100, Reinhard Tartler wrote:
> [EMAIL PROTECTED] (Sjoerd Simons) writes:
>
> > On Wed, Feb 21, 2007 at 03:48:08PM +0100, Reinhard Tartler wrote:
> >> Trent Lloyd <[EMAIL PROTECTED]> writes:
> >> > This check is done at IP up time because this is in no way a onc
Sjoerd Simons <[EMAIL PROTECTED]> writes:
> With newer versions of mdns it is indeed the case that only explicit .local
> lookups will fail.. With older version all hostname lookups would fail iff you
> had local in your search.
>
> So while the situation has improved, it's still quite bad to brea
On Wed, Feb 21, 2007 at 04:08:01PM +0100, Reinhard Tartler wrote:
> [EMAIL PROTECTED] (Sjoerd Simons) writes:
> > A second one could be done if resolvconf isn't available is to only
> > recheck when avahi is actually disabled, although this assumes that
> > the changes caused by bringing an interfa
[EMAIL PROTECTED] (Sjoerd Simons) writes:
> On Wed, Feb 21, 2007 at 03:48:08PM +0100, Reinhard Tartler wrote:
>> Trent Lloyd <[EMAIL PROTECTED]> writes:
>> > This check is done at IP up time because this is in no way a once-off
>> > check, it could vary from network to network
>>
>> Err, yes, the
[EMAIL PROTECTED] (Sjoerd Simons) writes:
> A second one could be done if resolvconf isn't available is to only
> recheck when avahi is actually disabled, although this assumes that
> the changes caused by bringing an interface down will never cause an
> nameserver to be added which has a .local.
On Wed, Feb 21, 2007 at 03:48:08PM +0100, Reinhard Tartler wrote:
> Trent Lloyd <[EMAIL PROTECTED]> writes:
> > This check is done at IP up time because this is in no way a once-off
> > check, it could vary from network to network
>
> Err, yes, there are broken networks in use out there. Is it rea
On Wed, Feb 21, 2007 at 11:32:23PM +0900, Trent Lloyd wrote:
> On Wed, Feb 21, 2007 at 02:28:37PM +0100, Reinhard Tartler wrote:
> > severity 409513 important
> >
> > On Sat, Feb 03, 2007 at 06:58:43PM +0100, Andrzej Zi??ba wrote:
> > > Configuring network interfaces at boot and deconfiguring at s
Trent Lloyd <[EMAIL PROTECTED]> writes:
> This check is done at IP up time because this is in no way a once-off
> check, it could vary from network to network
Err, yes, there are broken networks in use out there. Is it really the
job of random packages to check for random breakage?
> That said be
On Wed, Feb 21, 2007 at 02:28:37PM +0100, Reinhard Tartler wrote:
> severity 409513 important
>
> On Sat, Feb 03, 2007 at 06:58:43PM +0100, Andrzej Zi??ba wrote:
> > Configuring network interfaces at boot and deconfiguring at shut down
> > takes 10s or so.
>
> I see this as well.
>
> > I think t
severity 409513 important
On Sat, Feb 03, 2007 at 06:58:43PM +0100, Andrzej Zięba wrote:
> Configuring network interfaces at boot and deconfiguring at shut down
> takes 10s or so.
I see this as well.
> I think that the long time out at system shut down happens because
> avahi-daemon script is c
Package: avahi-daemon
Version: 0.6.16-2
Configuring network interfaces at boot and deconfiguring at shut down
takes 10s or so.
If I use 'ifdown -a' and next 'ifdown -a -v' I get the fallowing output:
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: exec
11 matches
Mail list logo
