From: Matthew Excell (matt_at_possibilityforge.com)
Date: Thu 03 Oct 2002 - 17:40:37 BST
Could this be related to something I saw several weeks ago with
PostgreSQL and slapd? Both of those daemons would bind to 0.0.0.0. I
discovered that it had to do with IPv6 being compiled into the kernel.
(or, rather, when I removed IPv6 from the kernel, the problem went
away. I guess it could have been one of the other programs that handles
IPv6 routing, etc.)
Matthew Excell
Senior Consultant
The Possibility Forge, Inc.
On Thu, 2002-10-03 at 02:48, kint_at_x-tincted.net wrote:
> On Wed, Oct 02, 2002 at 04:36:54PM -0500, Jacques Gelinas wrote:
> > When I execute donkey_s, without argument, I get
> >
> > Welcome to eDonkey2000 command line client v14.16.57.
> >
> > odd
> >
> now this is indeed odd, mine shows v16.16.59.
> perhaps you'll want me to email you the file privately?
>
> >
> > > This is basically the command I use to start it under a secure context.
> > > /usr/sbin/chbind --ip 192.168.0.1 \
> > > /usr/sbin/chcontext --secure --flag lock --flag nproc \
> > > /usr/lib/vserver/save_s_context /var/run/vservers/edonkey.ctx \
> > > /usr/lib/vserver/capchroot --nocapchroot . \
> >
> > Is there a typo here (the dot) ?
> >
> > > /home/kint/edonkey /bin/donkey_s auto - !
> >
> The dot is no typo, coz before this command I do something like
> cd /vservers/edonkey
> so . means the current dir
> (oh...now i see why u think it's a typo. The subsequent /home/kint/edonkey
> is a remnant of a deleted command because I do something like a chdir()
> wrapper, so that /bin/donkey_s will start in the working dir
> (/home/kint/edonkey) )
>
> instead of the complicated command above, i just do
> chbind --ip 192.168.0.1 ./donkey_s
>
> netstat -antlup | grep donkey_s
> tcp 0 0 192.168.0.1:4662 0.0.0.0:* LISTEN 3462/donkey_s
> udp 0 0 0.0.0.0:32898 0.0.0.0:* 3462/donkey_s