[nos-bbs] headless jnos consuming 100% CPU

Kerry Smith n3nxo at yahoo.com
Mon Mar 21 21:01:50 EDT 2011

I myself have only seen one instance where jnos would suck up 100% of the
CPU.  The incident your saying seems to be a total different problem.
BUT, maybe to shed a little bit of light, here is the problem I had and how I 
was able to correct it.
OS is Redhat 7.0.  Running nos like normal.  IF, and this is the BIG IF,
you have a port configured in the autoexec.nos file, that is going to a 
comm port with a TNC, it runs fine.  BUT, take the TNC off line and forget
to detach that port, and after a day, the CPU is at 100%.  If you leave a
TNC on that port, and turn off the radio, or even remove the radio, all is fine.
It's just that if you have a port configured to a tnc, make sure the tnc is there
and it's alive, not turned off.
Kerry - n3nxo

--- On Mon, 3/21/11, Harry Stone <harrystone at gmail.com> wrote:

From: Harry Stone <harrystone at gmail.com>
Subject: [nos-bbs] headless jnos consuming 100% CPU
To: nos-bbs at tapr.org
Date: Monday, March 21, 2011, 7:29 PM

When I compile JNOS with headless defined, it compiles fine and also runs fine until I start it and then log out of the machine.  After I log out, JNOS consumes 100% of cpu.  It seems like it still runs fine, although the machine is bogged down.  If I log into the machine and start JNOS and stay logged in, cpu usage is normal.  This seems to happen when it's started from an init script at boot too, almost like it's having problems any time it's not attached to a pty.  

Is there a #define I can change in the config header to make it spit out some debug info?  Please let me know if there's anything I can do to help troubleshoot this.  I've tested this on Slackware 13.1 and 12.2 with the same result.  I'm using the 20i source.  The Slackware machines are using the stock kernel from a vanilla "everything" install.  

Compile without headless defined results in a binary that runs perfectly from what I can tell.  I'm new to ham radio and packet but I've been using linux for some time.  

Thanks everyone for whatever help you can offer!


Have old memories and young hopes.

-----Inline Attachment Follows-----

nos-bbs mailing list
nos-bbs at tapr.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20110321/aa293e9d/attachment.html>

More information about the nos-bbs mailing list