On Thu, 20 Aug 2009, Daniel O'Connor wrote:
> Unfortunately the system is in Finland and I'm in Australia so I
> can't sit at the console :(
Someone visited the site and determined that the floppy drive cable was
intermittently fouling the CPU fan. I believe this was causing the CPU
to overheat
On Sat, 22 Aug 2009, Robert Watson wrote:
> On Sat, 22 Aug 2009, Daniel O'Connor wrote:
> > On Fri, 21 Aug 2009, CmdLnKid wrote:
> >> came back or the machine was rebooted. I continued for a while
> >> using /var/mail over NFS while setting or unset mail variables for
> >> the shell. You may also w
On Sat, 22 Aug 2009, Daniel O'Connor wrote:
On Fri, 21 Aug 2009, CmdLnKid wrote:
came back or the machine was rebooted. I continued for a while using
/var/mail over NFS while setting or unset mail variables for the shell. You
may also want to check into whether something is trying to acquire
On Fri, 21 Aug 2009, CmdLnKid wrote:
> came back or the machine was rebooted. I continued for a while using
> /var/mail over NFS while setting or unset mail variables for the
> shell. You may also want to check into whether something is trying to
> acquire a lock on a file over that NFS mount which
On Thu, 20 Aug 2009 08:42 -, doconnor wrote:
On Thu, 20 Aug 2009, Kostik Belousov wrote:
Things like ls on the console might take several seconds to respond
when the box didn't seem to be very busy (but wasn't idle, maybe
serving a little NFS). It wasn't the shell getting swapped out or
any
On Thu, 20 Aug 2009, Kostik Belousov wrote:
> > Things like ls on the console might take several seconds to respond
> > when the box didn't seem to be very busy (but wasn't idle, maybe
> > serving a little NFS). It wasn't the shell getting swapped out or
> > anything else obvious. This was on SMP,
On Thu, Aug 20, 2009 at 12:35:46PM +0100, Bob Bishop wrote:
>
> On 20 Aug 2009, at 12:06, Daniel O'Connor wrote:
>
> >On Thu, 20 Aug 2009, Daniel O'Connor wrote:
> >>On Thu, 20 Aug 2009, Bob Bishop wrote:
> >>>On 20 Aug 2009, at 08:25, Daniel O'Connor wrote:
> This is running in 6.2 ish using
On 20 Aug 2009, at 12:06, Daniel O'Connor wrote:
On Thu, 20 Aug 2009, Daniel O'Connor wrote:
On Thu, 20 Aug 2009, Bob Bishop wrote:
On 20 Aug 2009, at 08:25, Daniel O'Connor wrote:
This is running in 6.2 ish using 4BSD, I was under the impression
ULE wasn't very stable in 6.2.
I could proba
On Thu, 20 Aug 2009, Daniel O'Connor wrote:
> On Thu, 20 Aug 2009, Bob Bishop wrote:
> > On 20 Aug 2009, at 08:25, Daniel O'Connor wrote:
> > > This is running in 6.2 ish using 4BSD, I was under the impression
> > > ULE wasn't very stable in 6.2.
> > >
> > > I could probably try it though...
> >
>
On Thu, 20 Aug 2009, Bob Bishop wrote:
> On 20 Aug 2009, at 08:25, Daniel O'Connor wrote:
> > This is running in 6.2 ish using 4BSD, I was under the impression
> > ULE wasn't very stable in 6.2.
> >
> > I could probably try it though...
>
> Hmm. ISTR having similar problems around the 6.1-2 era. Yo
On 20 Aug 2009, at 08:25, Daniel O'Connor wrote:
This is running in 6.2 ish using 4BSD, I was under the impression ULE
wasn't very stable in 6.2.
I could probably try it though...
Hmm. ISTR having similar problems around the 6.1-2 era. You might try
6.4 if that's possible for you.
--
Bob
On Thu, 20 Aug 2009, Bob Bishop wrote:
> Hi,
>
> On 20 Aug 2009, at 03:34, Daniel O'Connor wrote:
> > [...]
> > The problem appears to now be that the userland process that reads
> > data
> > out of the kernel is being stalled for over 4 seconds. This process
> > reads from the kernel and does some
Hi,
On 20 Aug 2009, at 03:34, Daniel O'Connor wrote:
[...]
The problem appears to now be that the userland process that reads
data
out of the kernel is being stalled for over 4 seconds. This process
reads from the kernel and does some minor processing and then writes
it
out to a child pro
13 matches
Mail list logo
