OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
KB9MMA > NOSBBS   27.02.05 16:56l 71 Lines 2258 Bytes #999 (0) @ WW
BID : KB9MMA000266
Read: OE3GMW GUEST
Subj: nos-bbs Digest, Vol 7, Issue 7
Path: DB0FHN<DB0FOR<DB0SIF<DB0MW<DB0SWR<DK0WUE<DB0RES<ON0BEL<KP4IG<VE3FJB<
      WA7V<VE1JOT<N1OHX<W9BS<W9OTR<K9BBS<KB9MMA
Sent: 050223/0118Z @:KB9MMA.AMPR.ORG HamServ V2.66




   1. RE: The TUN Tunnel driver for JNOS - memory leak ! (Bob Lafont)
   2. RE: The TUN Tunnel driver for JNOS - memory leak !
      (maiko@pcs.mb.ca)

Message: 1
Date: Mon, 21 Feb 2005 18:39:40 -0600
From: "Bob Lafont" <blafont@frontiernet.net
Subject: RE: [nos-bbs] The TUN Tunnel driver for JNOS - memory leak !


I finally got around to removing IP encapsulation with Encap undefined. I was hoping this would stop the Jnos restarts mentione
d here but it has not. I am running Jnos on an Intel machine with Red Hat 9.0. RH does not restart, just Jnos. 

Does anyone have any suggestions on how I can track down the Jnos restarts?

73-Bob
WA2MNO


-----Original Message-----
From: nos-bbs-bounces@lists.tapr.org [mailto:nos-bbs-bounces@lists.tapr.org]
On Behalf Of maiko@pcs.mb.ca
Sent: Friday, December 17, 2004 10:44 AM
To: Bob Tenty; TAPR xNOS Mailing List
Subject: [nos-bbs] The TUN Tunnel driver for JNOS - memory leak !



Thanks to Bob (VE3TOK) for noticing this !

It *seems* that the use of the TUN interface causes the
amount of memory used by JNOS to grow, and you can actually
see it growing over a short period of time.

Sooooo, those of you using TUN may want to temporarily go
back to using the SLIP interface till I get this fixed, unless you have tons of memory to play with :-)

* no seriously, probably you should go back to slip for now.

Maiko Langelaar / VE4KLM


Hi Bob,

 Does anyone have any suggestions on how I can track down the Jnos 
 restarts?

When you have JNOS running, in a separate terminal or window, run the gdb utility (as root). If the JNOS pid is 27325 for examp
le, then run the gdb using 'gdb -p 27325'. It will STOP jnos and give you a prompt, just type 'continue' to let 
it go.

The next time JNOS restarts (because I assume it has crashed), hopefully the gdb will break out and you can then enter the comm
and 'where' or 'backtrace' and it will dump the place where the crash occurred type of thing. It would be helpfu
l to have the JNOS compiled with the -g debug option.

Another question, is this something you compiled yourself ? Did you compile it on the same machine you're running it on ?

Maiko



-- 
email: KB9MMA@KB9MMA.COM
ax25 : KB9MMA@KB9MMA.EN62.WI.USA.NA
Web site. http://www.KB9MMA.COM




Read previous mail | Read next mail


 09.04.2026 04:49:16lGo back Go up