On 12/05/2010 10:45 AM, Lowell Gilbert wrote:
Yuri y...@rawbw.com writes:
Beginning at some time less than 1 month ago I started getting such
message. Increasing maxproc doesn't help. Current values are like
this:
kern.maxproc: 6164
kern.maxprocperuid: 5547
What may be causing such
Yuri y...@rawbw.com writes:
Beginning at some time less than 1 month ago I started getting such
message. Increasing maxproc doesn't help. Current values are like
this:
kern.maxproc: 6164
kern.maxprocperuid: 5547
What may be causing such condition?
limits(1), perhaps?
Beginning at some time less than 1 month ago I started getting such
message. Increasing maxproc doesn't help. Current values are like this:
kern.maxproc: 6164
kern.maxprocperuid: 5547
What may be causing such condition?
Yuri
--- sample log from portupgrade ---
mv -f .deps/regex.Tpo
A prt of my daily security run:
triton.xxx.xxx.xxx kernel log messages:
+++ /tmp/security.VnqB8ZT6 2008-10-27 23:53:32.0 +0100
+em0: link state changed to DOWN
+em0: link state changed to UP
+em0: link state changed to DOWN
+em0: link state changed to UP
+em0: link state changed to
On Tue, Oct 28, 2008 at 05:26:03PM +0100, Jos Chrispijn wrote:
A prt of my daily security run:
triton.xxx.xxx.xxx kernel log messages:
+++ /tmp/security.VnqB8ZT62008-10-27 23:53:32.0 +0100
+em0: link state changed to DOWN
+em0: link state changed to UP
+em0: link state changed
Jeremy,
Uit een eerder bericht (28-10-2008 17:32):
No, because the messages are in the kernel log. The kernel itself does
not print timestamps, because that's silly.
Yes that is .true.
Try doing this:
Great, will do that! No 'watchdog timeout' events yet :-)
thanks for sharing,
Jos
On Tuesday 28 October 2008 17:32:36 Jeremy Chadwick wrote:
On Tue, Oct 28, 2008 at 05:26:03PM +0100, Jos Chrispijn wrote:
A prt of my daily security run:
triton.xxx.xxx.xxx kernel log messages:
+++ /tmp/security.VnqB8ZT6 2008-10-27 23:53:32.0 +0100
+em0: link state changed to
I posted about this a few days ago and its appeared again
in my security log (the backup routine log appears to be
fine)
+(sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0
+(sa0:ahc0:0:6:0): CAM Status: SCSI Status Error
+(sa0:ahc0:0:6:0): SCSI Status: Check Condition
In the last episode (May 13), Graham Bentley said:
I posted about this a few days ago and its appeared again in my
security log (the backup routine log appears to be fine)
+(sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0
+(sa0:ahc0:0:6:0): CAM Status: SCSI Status Error
hi,
on my freebsd 4.x box I get no matching session as an kernel log. I
was wondering what this could mean.
thx in advance
christian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
Hello,
I did post this to -current a few days ago, but having got no
response, perhaps here is a better place for it.
I've also noted a few previous attempts to get an answer to this
question on freebsd-questions in January and February, but nobody
replied. This doesn't seem to be an isolated
On Mon, 8 Dec 2003, Michael A. Alestock wrote:
What does this message mean??...
No debugger in kernel
Dec 8 17:40:05 bsd /kernel: No debugger in kernel
I hope it isn't anything serious???
I haven't changed or altered anything in a long time.
It probably means you accidentally typed the
What does this message mean??...
No debugger in kernel
Dec 8 17:40:05 bsd /kernel: No debugger in kernel
I hope it isn't anything serious???
I haven't changed or altered anything in a long time.
___
[EMAIL PROTECTED] mailing list
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known prank?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body
[redirected to -current]
On Tuesday, 4 February 2003 at 17:55:42 -0800, [EMAIL PROTECTED] wrote:
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known
Each time I send an email using Mutt the following message pops up on the screen:
/kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1572
What could be the cause?
Using a freshly loaded v4.7 running IPFW with the following in rc.conf
firewall_type="open" #wide open when using
On Fri, 31 Jan 2003, Kjell wrote:
Each time I send an email using Mutt the following message pops up on
the screen:
/kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1572
What could be the cause?
TCP port 113 is the Auth service. When you send mail, sendmail will
attempt
From: adrian kok [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 18, 2002 11:55 AM
Subject: kernel message
Hi all
I received the following message from /var/log
What is this meaning?
Sep 17 12:33:04 mail /kernel: pullup failed
i guess your kernel just doesnt work out
a meaningful log entry.
Fragmented packets like that are probably due to broken hardware on
your network, although they can be the result of enemy action
-CM
- Original Message -
From: adrian kok [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 18, 2002 11:55 AM
Subject: kernel
19 matches
Mail list logo
