Hi,
Christoph Egger wrote:
> Interestingly we never had that on our hardware server (public IPv4
> addresses and sshd listening). However I just whitnessed it again on my
> kFreeBSD vserver.
I experienced it on real amd64 hardware, some Athlon X2 or early
Opteron. Only ever saw it happen on that
Hi!
I have had success with logging in + out again which seems to recover
the machine -- I always seem to be able to get logged in and to a
rootshell and logging out + in again gets rid of the maxproc limit
problem
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Develop
Christoph Egger writes:
> I have had success with logging in + out again which seems to recover
> the machine -- I always seem to be able to get logged in and to a
> rootshell and logging out + in again gets rid of the maxproc limit
> problem
Interestingly we never had that on our hardware server
Christoph Egger writes:
> I have had success with logging in + out again which seems to recover
> the machine -- I always seem to be able to get logged in and to a
> rootshell and logging out + in again gets rid of the maxproc limit
> problem
Logging in using the libvirt serial connection or the
Dear kfreebsd people,
jessie 8.1 point release is out [0].
However, there is no such a point release for jessie-kfreebsd.
For example, the base-files package is still version 8.
It seems that jessie-kfreebsd-pu is not working yet.
Anyway, thanks for your work.
[0] http://ftp.debian.org/debian/
5 matches
Mail list logo
