On Wed, 10 Dec 2014 14:52:59 -0800, Dave Taht said:
> I am interested in long term memory leakage (run a free),
> process usage (runaways like pimd), and growth in disk space usage (df),
> so output like

root@bogon-gateway-1:~# uptime
 14:31:39 up 33 days,  8:50,  load average: 0.02, 0.05, 0.05
root@bogon-gateway-1:~# free
             total         used         free       shared      buffers
Mem:        126256       100732        25524            0         6156
-/+ buffers:              94576        31680
Swap:            0            0            0
root@bogon-gateway-1:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                    7296       392      6904   5% /
/dev/root                 7680      7680         0 100% /rom
tmpfs                    63128     49364     13764  78% /tmp
/dev/mtdblock5            7296       392      6904   5% /overlay
overlayfs:/overlay        7296       392      6904   5% /
tmpfs                      512         0       512   0% /dev

Biggest issue after 33 days of uptime seems to be /tmp/log/babeld.log:

root@bogon-gateway-1:~# ls -l /tmp/log/babeld.log
-rw-r--r--    1 root     root      49416018 Dec 11 14:34 babeld.log
root@bogon-gateway-1:~# wc /tmp/log/babeld.log
   772310   6176740  49416530 /tmp/log/babeld.log
root@bogon-gateway-1:~# sort /tmp/log/babeld.log | uniq -c

Oh kewl.  That seems to have killed it :)

Uptime is now 11 minutes, and the log is much shorter.

root@bogon-gateway-1:~# sort /tmp/log/babeld.log | uniq -c
    107 Couldn't determine channel of interface sw00: Invalid argument.
    107 Couldn't determine channel of interface sw10: Invalid argument.

I'm trying to remember why I even want babeld running.  In any case,
the log as it stands now those two messages aren't much help.