According to Gerd: While burning my CPU.
>
> Hello all,
>
> To test the other services on the machine we tried to connect to
> our node (AWZnode). The node came up as usual but showed no
> reaction to any input.
>
> What we found out were some strange things on the Linux
> machine. The first thing was that the system's clock did not have
> the correct time and date. Obviously, there was something wrong
> with the clock. The machine today had a system date of April 8th.
> Could it be that running Linux over a couple of weeks without
> restarting has influences on the system's clock?
I use 'netdate' to sync the clock from another server to prevent problems.
>
> The second thing was more interesting: The mheard data file
> /var/ax25/mheard/mheard.bin had grown up to 56 MBytes!
> After deleting this file AWZnode resumed working.
> Question here: How can this be avoided? Is there a way to
> configure mheardd to set a maximum size for its data file?
> At the moment, we have set up a crontab entry so that the file now
> is deleted once in a month. Is this really the way to go or are there
> more options?
Use the -n option
mheardd -l -f -n25
-l log calls
-f delets the old file when starting mheardd
-n25 shows the last 25 hraed calls only.
That keeps the mheard.dat file under 1k.
>
> In the hope that someone has got the one or the other hint for
> solving these problems,
>
> Best regards, 73
>
> Gerd
>
--
Regards Richard.
[EMAIL PROTECTED]
