[nos-bbs] please remind me of JNOS features asked for inthe past ...

[Michael Fox - N6MEF]

No sweat.

Here's what we use:

trace  p144  0111  ./logs/trace.p144  1000

Where:
p144 is the interface name
0111 is the trace level
./logs/trace.p144 is the file name
1000 is the sync interval in 1/1000 sec.  

When Maiko developed the code, we tested with 3 ports running at 1/2 second
sync (500).  I think we also tried 1/4 second - but I don't recall.  Anyway,
there was no issue running on a little Atom 330 processor. 

We do a logrotate on them daily and maintain 30 days-worth, each with a date
extension.  The Ubuntu /etc/logrotate.d/jnos file contains entries such as:

/opt/jnos/logs/trace.p144 {
   rotate 30
   daily
   dateext
   copytruncate
   missingok
   ifempty
}

Michael

-----Original Message-----
From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
Of ve1bf
Sent: Tuesday, December 20, 2011 5:19 PM
To: TAPR xNOS Mailing List
Subject: Re: [nos-bbs] please remind me of JNOS features asked for inthe
past ...

thanks michael I didn't know that...will give that a try merry
xmas...73..art
----- Original Message -----
From: "Michael Fox - N6MEF" <n6mef at mefox.org>
To: "'TAPR xNOS Mailing List'" <nos-bbs at tapr.org>
Sent: Tuesday, December 20, 2011 12:56 PM
Subject: Re: [nos-bbs] please remind me of JNOS features asked for inthe
past ...


> Art,
>
> Here's a way to do close to what you want - at least on linux :
> 1)  Direct your trace output to a file
> 2)  View the file with "tail -f <filename>" in another window
>
> We direct the trace for each interface (either 3 or 4 on each of our 
> BBSs) to a separate trace file.  With the change Maiko made about a 
> year ago, the output to the trace file is real time.  We also do a 
> logrotate and save the prior 30 days of traces so we can go back and 
> review a problem that's
> reported later.   More often than not, we hear about the problem later and
> this saves us from having to try to recreate the situation.  ("hey, 
> Michael, I had a problem with ... last night ...").  Works FB!
>
> Michael
>
>
> -----Original Message-----
> From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On 
> Behalf Of ve1bf
> Sent: Tuesday, December 20, 2011 8:45 AM
> To: TAPR xNOS Mailing List
> Subject: Re: [nos-bbs] please remind me of JNOS features asked for in 
> the past ...
>
> Makio first of all thanks for all you have done and are doing with the 
> jnos ..I know it takes up a great deal of your time...
> I would like to see a second trace window that I can watch just one 
> port example hf port on it own and the others coming in on the f9 
> screen. I think it would be helpful in tracking a problem ...just an 
> idea btw Merry Christmas all...73...Art
> ----- Original Message -----
> From: "Maiko Langelaar" <maiko at pcs.mb.ca>
> To: "TAPR xNOS Mailing List" <nos-bbs at tapr.org>
> Sent: Tuesday, December 20, 2011 12:40 PM
> Subject: Re: [nos-bbs] please remind me of JNOS features asked for in 
> the past ...
>
>
>>
>>> implementing into JNOS2 the following commands and allowing the use 
>>> of dynamic host addresses along with the (actual) 'only' fixed IP
>>
>> Maybe I am misunderstanding you Gus, but you already can do this.
>>
>>  JNOS allows for dynamic host addresses and custom UDP source  and 
>> destination ports for any AXIP and AXUDP interfaces.
>>
>> Maiko
>>
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
> 


_______________________________________________
nos-bbs mailing list
nos-bbs at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs