hello
I already rebooted the machine so I can't check this anymore on a live system,
but as you said, the clock was out of sync 10 minutes from what it sould, I
activated timesync again ( /proc still shows the same incorrect date).
Also i did a snap of a broken proc a day before I found the mac
On Wed Jul 22 11:49:54 EDT 2009, s...@plan9.bell-labs.com wrote:
> Very odd. There are no blocking operations in reading the status file in
> /proc.
> The only thing I can think of is that you have something bound (snapfs?) in
> /proc
> and that you're hanging on a stale mount point.
>
> Is the
Very odd. There are no blocking operations in reading the status file in /proc.
The only thing I can think of is that you have something bound (snapfs?) in
/proc
and that you're hanging on a stale mount point.
Is the clock set properly on that machine?
Sape
> hello
>
> today i found 9g
On Mon Jul 20 04:11:39 EDT 2009, gd...@9grid.es wrote:
> hello
>
> today i found 9grid plan9 under heavy load, stats reports load ~2000, syscall
> ~6, context ~22000, i was trying to discover which proc has gone crazy,
> but i can't even complete a ps. I can do other operations, such as send
hello
today i found 9grid plan9 under heavy load, stats reports load ~2000, syscall
~6, context ~22000, i was trying to discover which proc has gone crazy, but
i can't even complete a ps. I can do other operations, such as sending this
email over drawterm, run stats, netstat, read the logs,
