Displaying 3 results from an estimated 3 matches for "memcheck86".
Did you mean:
memcheck
2004 Aug 06
1
icecast2/ices2 , 7o minutes and crash
...ng X means that the graphics side won't be the cause (can be
> awkward). I would suspect heating for the moment, I had similar problems
> some time ago and problems such as not burning CDs correctly until a put
> a fan in. Another key thing to check is memory, there's a util
> memcheck86 (IIRC) to do this, but building a large optimised program
> like the kernel with -j N can be quite good as well (make N something
> like 4).
wow . you were right on .. i installed a new fan last night . i've been
running icecast2/ices2 for half-a-day already _ more than 10x longer than...
2004 Aug 06
2
icecast2/ices2 , 7o minutes and crash
> On Wed, 2002-12-11 at 19:50, Adon Irani wrote:
> >
> > hello .,
> >
> > i've got icecast2/ices2 (libshout/libao ) compiled/running from cvs .
> This sound like some instability of the kernel/X/hardware rather than
> ices/icecast. If by tty's you mean the console then they can switch
>
> I would check the system logs (/var/log/messages) first for
2004 Aug 06
0
icecast2/ices2 , 7o minutes and crash
...s sakes .
Not running X means that the graphics side won't be the cause (can be
awkward). I would suspect heating for the moment, I had similar problems
some time ago and problems such as not burning CDs correctly until a put
a fan in. Another key thing to check is memory, there's a util
memcheck86 (IIRC) to do this, but building a large optimised program
like the kernel with -j N can be quite good as well (make N something
like 4).
> > If it still happens then just check what happens to the processes over
> > that period of time. vmstat 1 is usually good.
>
> i expected...