[pskmail] Re: fldigi, log files and the monitor

  • From: Fred Reiselt <freiselt@xxxxxxxxxxxxx>
  • To: pskmail@xxxxxxxxxxxxx
  • Date: Fri, 03 Oct 2008 18:44:13 -0500

Per,

You are a gentleman, a scholar, and a great coder... along with Rein, Roberto, W1HKJ and others that help make this great project successful.

Thank you and everyone else for the great teamwork world-wide.

73,
Fred - wb5con

Pär Crusefalk wrote:
Hi all,

I have had some interesting issues to deal with regarding fldigi and its
log. I reported earlier that I had double characters and what not in the
log from fldigi, turned out I got a nice and clean log if I shut down
the pskmail server. As soon as I started the server the log file would
go berzerk agn. I started looking for reasons and among things I deleted
a symlink to the fldigi.log file (called gMFSK.log, used to have the
cron job and the gmfsk.php page happy). Now I can have both the pskmail
server and fldigi up and the log is fine. There must be something
looking for gMFSK.log somewhere in the server, but I havent looked for
it yet.

So, I then proceeded to update the gmfsk.php page. That page is also
used in Robertos monitor and there were some issues regarding maximum
file sizes and empty lines with fldigi 3. The original php code was
written just to have something on a web page and I just left it when it
worked. A rewrite was long overdue.. The old code would read the entire
log file and split it into an array, naturally a large file would take
time to handle that way (exceeding the maximum allowed time when the
file grew too big). The new code is more like a tail, it moves to the
end of the file and works its way up x no of lines from there. So, the
file can be really big and it shouldn't take much longer anyway.

I have it up and running here:
http://www.crusefalk.se/gmfsk/index.php?lines=30&refresh=10

I will clean it up and upload it tomorrow (gotta sleep now).

73 de Per, sm0rwo



------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.5/1706 - Release Date: 10/3/2008 6:17 PM


Other related posts: