Trond Davidsen writes:
> > If you can get mpd into a state where "kill -9" doesn't kill it,
> > then that seems like a kernel bug to me, and so we should probably
> > hone in on that first.. maybe we can come up with a simple test
> > case, e.g. using the event library debug output, write a progr
>
> Hmm.. well, we should try to pick this apart one problem at a time.
>
> If you can get mpd into a state where "kill -9" doesn't kill it,
> then that seems like a kernel bug to me, and so we should probably
> hone in on that first.. maybe we can come up with a simple test
> case, e.g. using
Trond Davidsen writes:
> > Those two events correspond to the netgraph data and control sockets
> > associated with the bundle. Not sure how important that is..
> > the ng_socket(4) code relies on the standard generic socket code
> > so unlikely that the problem lies there.
> >
> > The fact that
>
> Those two events correspond to the netgraph data and control sockets
> associated with the bundle. Not sure how important that is..
> the ng_socket(4) code relies on the standard generic socket code
> so unlikely that the problem lies there.
>
> The fact that it's blocked on "piperd" implie
Trond Davidsen writes:
> just an update. I've been debugging a little more and found that mpd
> hangs hard,top shows mpd's state as 'piperd', when it got over 128
> sockets open. This sounds like some kind of system limit to me, any
> ideas anyone?
>
> I've enbled the '#define DEBUG_EVENT'
Hi,
just an update. I've been debugging a little more and found that mpd
hangs hard,top shows mpd's state as 'piperd', when it got over 128
sockets open. This sounds like some kind of system limit to me, any
ideas anyone?
I've enbled the '#define DEBUG_EVENT' in the file 'event.c' in the mp
Archie Cobbs wrote:
>
> I think this error must be coming from the socket code. I wonder
> if increasing the receive buffer size on the netgraph socket would
> help.. try this patch for example:
>
> Index: main.c
> ===
> RCS file:
Trond Davidsen writes:
> When I try to make 240 bundles, from the log, it seems mpd is makeing
> all the nodes ok, but when I try to establish a connection nothing
> happens, no respons, nothing in the log, and mpd is frozen and needs to
> be killed with kill -9. And then it leaves 720 nodes b
Trond Davidsen wrote:
>
> When I create 240 bundles, mpd creates 720 netgraph nodes.
> Is there a limit on how many nodes the netgraph system can handle?
> Where is the netgraph system defined? i can find the modules under
> /usr/src/sys/modules/netgraph, but I can't find the 'netgraph base sys
Archie Cobbs wrote:
>
> One problem with netgraph is that node and hook names can only be about 15
> characters.. so when you get to 100 bundles, the hook names start
> overflowing the buffers.
>
> If you're only running one version of mpd, for example, you can
> try this patch to fix the '100
Trond Davidsen writes:
> I'm trying to set up mpd as a replacement for poptop + ppp. But I run
> into a problem when I try to configure more than 100 bundles. When I
> configure 30 bundles, everything works nicely. When I configure 100
> bundles, things seems to work nicely, but when I run n
Julian Elischer wrote:
>
> Did archie get back to you on this one?
>
No.
Trond
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
Did archie get back to you on this one?
On Wed, 24 Oct 2001, Trond Davidsen wrote:
> Hi,
> some info about the machine:
>
> vpn-gw2# uname -a
> FreeBSD vpn-gw2 4.4-STABLE FreeBSD 4.4-STABLE #2: Tue Oct 16 16:42:27
> CEST 2001 root@vpn-gw2:/usr/obj/usr/src/sys/VPN-GW2 i386
> vpn-gw2#
>
Hi,
some info about the machine:
vpn-gw2# uname -a
FreeBSD vpn-gw2 4.4-STABLE FreeBSD 4.4-STABLE #2: Tue Oct 16 16:42:27
CEST 2001 root@vpn-gw2:/usr/obj/usr/src/sys/VPN-GW2 i386
vpn-gw2#
The machine is a dual 700MHz PIII with 512MB ram and 3 3c905B nics.
/etc/sysctl.conf looks like this:
14 matches
Mail list logo
