I have a FreeBSD server (was 5.4-prerelease, now 6-stable as of noon PDT).
On this server I got a problem with sshd throwing signal 6:
Jul 18 15:04:03 log01 sshd[66161]: debug2: User child is on pid 66163
Jul 18 15:04:03 log01 sshd[66163]: debug3: PAM: opening session
Jul 18 15:04:03 log01 sshd[66
John Von Essen wrote:
> Doug,
>
> Did some googling and I did find a connection between excessive
> CLOSED_WAITS, and hanging apache, and webbots. Some of the IP's I saw in
> my netstat were bots too. The problem has something to do with the bot
> no longer accepting data, but apache will continue
On Tuesday 18 July 2006 13:04, Gareth McCaughan wrote:
> On Tuesday 2006-07-18 16:54, Deomid Ryabkov wrote:
> > Gareth McCaughan wrote:
> >
> > > About 6 minutes after booting (on three occasions, but I
> > > don't guarantee this doesn't vary), a process (well, a
> > > kernel interrupt thread, I g
Doug,
Did some googling and I did find a connection between excessive
CLOSED_WAITS, and hanging apache, and webbots. Some of the IP's I saw in
my netstat were bots too. The problem has something to do with the bot no
longer accepting data, but apache will continue to send it back since the
bo
John Von Essen wrote:
> Had a little crash today, that appears to be apache related, but is
> confusing nonetheless.
>
> My server hosts a fair amount of websites, but nothing crazy. Uptime is
> usually only 0.5. Anyway, it got real slow, when I finally logged in,
> uptime was 152, ps -aux showed
Had a little crash today, that appears to be apache related, but is
confusing nonetheless.
My server hosts a fair amount of websites, but nothing crazy. Uptime is
usually only 0.5. Anyway, it got real slow, when I finally logged in,
uptime was 152, ps -aux showed alot of apache pids, over a 10
On Tuesday 2006-07-18 16:54, Deomid Ryabkov wrote:
> Gareth McCaughan wrote:
>
> > About 6 minutes after booting (on three occasions, but I
> > don't guarantee this doesn't vary), a process (well, a
> > kernel interrupt thread, I guess) that appears in the
> > output of "ps" as "[swi4: clock sio]"
> "matt" == matt <[EMAIL PROTECTED]> writes:
[ responding to my lack of tun routing ]
matt> Have you set net.inet.ip.forwarding=1 via sysctl?
yes.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hack
Gareth McCaughan wrote:
About 6 minutes after booting (on three occasions, but I
don't guarantee this doesn't vary), a process (well, a
kernel interrupt thread, I guess) that appears in the
output of "ps" as "[swi4: clock sio]" begins to use
about 3/4 of the machine's CPU.
I recall seeing simi
> The man pages of if_tun are out-of-date in some respects, but with
> comments from the group and reading the sources of ppp, I have worked
> around most of the problems I've found. However, I'm stuck with one
> quandry. My tunnel setup process produces the following:
>
> tun0: flags=8051 mtu 15
On Tue, Jul 18, 2006 at 11:24:00AM +0200, Michael Reifenberger wrote:
> Hi,
> with a via epia EN-15000 MB and an U160 scsi disk I get with eli(4) I get
> ~27-40MB/s read/write performance trough eli(4) with AES265 key.
>
> cryptotest gives:
> (totum)(root) ./cryptotest -a aes256 10 4096
> 7.8
John Baldwin wrote:
Interrupt storm detected on "irq18: uhci2"; throttling interrupt source
which ties to the disk interrupt. Will that be slowing things down?
Would increasing the storm threshold help (especially disk
performance)? Guess I'm looking for any mitigation that might be
Hi,
with a via epia EN-15000 MB and an U160 scsi disk I get with eli(4) I get
~27-40MB/s read/write performance trough eli(4) with AES265 key.
cryptotest gives:
(totum)(root) ./cryptotest -a aes256 10 4096
7.838 sec, 20 aes256 crypts,4096 bytes, 104511751 byte/sec, 797.4
Mb/sec
(I've asked this question on -questions and -stable, with no success;
hence I'm taking it to the assembled wizardry of -hackers. A bit of
googling suggests that I'm far from the first person to have had a
similar problem, though it seems to be worse for me than for the
others I've found.)
I have a
Quoting Avleen Vig <[EMAIL PROTECTED]> (from Mon, 17 Jul
2006 22:36:26 -0700):
On Mon, Jul 17, 2006 at 04:14:14PM +0930, Benjamin Close wrote:
Which implements a boot menu item, sysctl tunable (hw.inflight_mode) and
prevents all wireless & bluetooth drivers from attaching (probe succeeds
stil
15 matches
Mail list logo
