<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal>Maiko,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Here’s some more info on the problem with delayed
writing to trace files. (You’re probably tired of hearing from me
on this, but I figured you can always use more specific data). <span
style='font-family:Wingdings'>J</span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have a test machine set up with 3 ports but one has no
radio connected. It’s sending beacons every 30 minutes but, of
course, hears nothing on that one port. So the trace file consists of
only outgoing beacon packets. Trace level is set to 0111. The file
is 12 hours behind!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Another port sits on a frequency shared by a couple other
BBSs. At night, there are beacons from all three machines, plus some low
levels of traffic. Trace level is also set to 0111. This morning,
when I check the machine, the file was 4 hours behind!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I started a ping to one of the other BBSs on that
port: “ping xxx 56 10000” for a 10,000 ms gap between
pings. After a while, I got the idea of using tail –f. So I
opened another terminal session and did a “tail –f” on the
trace file to see when it was being written. It was written after
packets, 26, 34, 46, 54, 63, … or about every 9-10 pings or about
every 90-100 seconds. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Now, the machine can capture tcpdump or tshark trace output
on-the-fly, at Ethernet speeds. So it should be able to easily write
trace output for a 1200 baud connection as it happens – just like it
already does to the screen.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I understand that some implementations of JNOS may be
running on very old machines, although I find it difficult to believe that they
wouldn’t be able to keep up with 1200 baud. Anyway, let’s
assume they can’t. Perhaps it would be possible to add a write
delay parameter to the config file? Set it to zero and it sends info to
the file system at the same speed it writes to the screen. Suggest a
value that would slow it down to its current crawl – perhaps even make
that the default, for backward compatibility.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I hope that’s useful.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Michael<o:p></o:p></p>
<p class=MsoNormal>N6MEF<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>P.S. A couple of us have been running the
“I” release and no problems so far. Of course, we
haven’t had it running for 25 days yet, so can’t comment on the
timer fix yet.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>