[Cerowrt-devel] how is everyone's uptime?
Joseph Swick
cerowrt at decoy.cotse.net
Thu Dec 11 20:30:15 EST 2014
On 12/10/2014 05:52 PM, Dave Taht wrote:
> the lab where I was keeping a box up under load had a long enough
> power failure last week to keeelll my approximatively 76 days uptime.
>
> Anybody else got any record-holders here?
>
> 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
>
> uptime
> free
> df
>
> periodically would be nice.
>
(Hopefully this gets through) Here's mine:
root at gw:~# uptime
01:10:07 up 117 days, 1:43, load average: 0.26, 0.17, 0.12
root at gw:~# free
total used free shared buffers
Mem: 126256 55744 70512 0 6240
-/+ buffers: 49504 76752
Swap: 0 0 0
root at gw:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 7296 404 6892 6% /
/dev/root 7680 7680 0 100% /rom
tmpfs 63128 1272 61856 2% /tmp
/dev/mtdblock5 7296 404 6892 6% /overlay
overlayfs:/overlay 7296 404 6892 6% /
tmpfs
However, while I'm getting an IPv6 address from Comcast, I don't have
IPv6 working inside, and I see this regularly in my logs:
Fri Dec 12 01:23:53 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!
Fri Dec 12 01:23:54 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on se00 thus we don't announce a
default route!
Fri Dec 12 01:23:58 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!
Fri Dec 12 01:23:59 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on se00 thus we don't announce a
default route!
Fri Dec 12 01:24:02 2014 daemon.warn odhcpd[1289]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!
I had tried to send a message to the list about it a while back, but I
think it may have gone to the bit-bucket due to how I setup my email
aliases (hoping the same fate doesn't happen to this message). At the
time I thought it may have been PLEBKAC (mine), but I think there's been
a few others who have posted similar error messages. I just haven't had
a whole lot of time to try to investigate myself, so I've just been
continuing to live with just IPv4.
-- Joseph Swick
More information about the Cerowrt-devel
mailing list