#include <hallo.h>
* Jesús M. Navarro [Tue, Aug 31 2010, 09:12:44PM]:

> > * Jesús M. Navarro [Tue, Aug 31 2010, 03:57:15PM]:
> > > BindAddress: 127.0.0.1 192.168.0.1
> > >
> > > Then, the cron.daily script will fail with the following error:
> > >
> > > mithrandir:/etc/apt-cacher-ng# /etc/cron.daily/apt-cacher-ng
> > > Cannot connect, no alternative (socket file) available
> > > no such host: 127.0.0.1192.168.0.1
> >
> > I think there is junk in your line mentioned above, maybe unprintable
> > chars?
> 
> As per vim, there's no junk in that line.  Just in case I deleted it and 
> rewrited it from scratch.  Same results, so it seems it's a "real" bug.

Ok, now I start remembering more details. This bug existed but it's
about the parser for this line. In the caller script. It has nothing to
do with port binding (in the daemon). The only relation to binding is
the name of the option being read there. I think the problem has been
fixed in 0.3.1 almost two years ago. 

I hope you see the story of my relation to the Emperor, besides of being
a human.

> > Anyhow, this bug cannot fixed in Stable.
> 
> It's a bug, nevertheless.
> 
> And there *might* be ways to resolve it in Stable (i.e.: changing the comment 

Debian does not fix non-critical bugs in non-essential packages in
Stable. That's a simple rule.

> > Try the backport from
> >
> > http://www.unix-ag.uni-kl.de/~bloch/acng/download/backports/
> 
> The package from that backport works with the same configuration than the old 
> from Stable (at least on my box) and doesn't exhibit the bad behaviour: it 
> does bind to both 127.0.0.1 and 192.168.0.1 without errors.
> 
> Cheers.

Nice, thanks.

Eduard.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to