so i had another systat complete freeze, this time
remotely, so again, no dump...
sorry about another useless report, but looking at the
mailing list looks like other people are experiencing
hangs during disk activity.
(i am speculating in this direction simply because
systat's first screen after
hmm, on Sun, May 06, 2012 at 12:38:49PM -0700, Philip Guenther said that
> On Sun, May 6, 2012 at 3:38 AM, frantisek holop wrote:
> ...
> > however on the other notebook systat froze the system solid.
> > i have no idea how to reproduce this, obviously, running
> > systat now works fine.
>
> Coul
On Sun, May 6, 2012 at 3:38 AM, frantisek holop wrote:
...
> however on the other notebook systat froze the system solid.
> i have no idea how to reproduce this, obviously, running
> systat now works fine.
Could you see the machine's console and see whether it paniced?
For those that are interes
Hi,
frantisek holop wrote:
| hi there,
[.]
| could the reason be, that after the update both
| libkvm.so.13.0 and libkvm.so.13.1 were still under /usr/lib?
The dynamic linker will use the first library it encounters to
resolve the symbols (which can be used for nice tricks via some
LD_PRE
hi there,
i was copying using rsync between two openbsd notebooks
on LAN, and i tried to run systat on both of them to try
and see why the transfer speed hovered around 700KB/s
both notebooks are -current.
first i ran it on the receiving machine, no problem.
however on the other notebook systat
5 matches
Mail list logo
