public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Memory leak
Date: Sun, 20 Jan 2008 12:13:19 +0100	[thread overview]
Message-ID: <200801201213.19923.axel@open-mesh.net> (raw)
In-Reply-To: <20080117140452.sf4w0jir48sgwsw0@webmail.ddmesh.de>

Hi,

can you check if the problem is fixed with rv 957.

regards,
axel

On Donnerstag 17 Januar 2008, Freifunk Dresden wrote:
> Hi,
>
> has anyone could verify the memory-leak problem (see previous thread).
> I'm currently use the -one-way-tunnel which does not destroy/recreate
> the gw thread that is causing the memory consumtion.
>
> jfi: the system is whiterussian rc6, busybox 1.7.2/1.8.2, uclibc 0.27.
> I still couldn't get uclibc 29 running to check if this causes the problem.
> Can somebody check this or first verify the problem?
>
> /Stephan
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n



  reply	other threads:[~2008-01-20 11:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  9:57 [B.A.T.M.A.N.] Memory leak Freifunk Dresden
2008-01-04 20:24 ` Axel Neumann
2008-01-05 20:47   ` Freifunk Dresden
2008-01-06 14:03     ` Axel Neumann
2008-01-06 15:52       ` Freifunk Dresden
2008-01-07  9:45         ` Axel Neumann
2008-01-07 12:56           ` Freifunk Dresden
2008-01-07 16:48             ` [B.A.T.M.A.N.] one-way / two-way tunnel (was: Memory leak) Axel Neumann
2008-01-07 20:52               ` Freifunk Dresden
2008-01-10  8:25               ` Freifunk Dresden
2008-01-17 13:04   ` [B.A.T.M.A.N.] Memory leak Freifunk Dresden
2008-01-20 11:13     ` Axel Neumann [this message]
2008-01-26 21:04       ` Freifunk Dresden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801201213.19923.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox