Hi,
I've updates my system this morning after reading about the usb mfc. The
sources used before are dated from january. I'm not sure if this error
was triggered by the update, but:
Using sysctl -a it seems to lose track after some lines.
snip
kern.ostype: FreeBSD
kern.osrelease: 4.11-STABLE
On Wed, Apr 27, 2005 at 07:46:28PM +0200, Marc Santhoff wrote:
Hi,
I've updates my system this morning after reading about the usb mfc. The
sources used before are dated from january. I'm not sure if this error
was triggered by the update, but:
Using sysctl -a it seems to lose track after
Am Mi, den 27.04.2005 schrieb Marc Olzheim um 20:10:
On Wed, Apr 27, 2005 at 07:46:28PM +0200, Marc Santhoff wrote:
Hi,
I've updates my system this morning after reading about the usb mfc.
The
sources used before are dated from january. I'm not sure if this
error
was triggered by the
On Wed, Apr 27, 2005 at 08:24:36PM +0200, Marc Santhoff wrote:
That is 'kern.msgbuf' ;-)
Hm, I've never seen such a verbose output before.
Has anything changed in that area? And why does it still occur after a
reboot, normally buffers are only temporarily valid(at least I thought
so
Am Mi, den 27.04.2005 schrieb Marc Olzheim um 20:31:
On Wed, Apr 27, 2005 at 08:24:36PM +0200, Marc Santhoff wrote:
That is 'kern.msgbuf' ;-)
Hm, I've never seen such a verbose output before.
Has anything changed in that area? And why does it still occur after a
reboot, normally
On Wed, Apr 27, 2005 at 08:53:57PM +0200, Marc Santhoff wrote:
I still don't understand completly. In the file made like this:
sysctl -a garbage.txt
there are the messages of at least three reboot cycles.
The kernel tries to preserve the message buffer if it has not been
cleared by
