From: Christian Schmid <webmaster@rapidforum.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com
Subject: Re: ARGH MORE BUGS!!!
Date: Tue, 22 Feb 2005 01:10:46 +0100 [thread overview]
Message-ID: <421A7886.8060302@rapidforum.com> (raw)
In-Reply-To: <20050221213610.GC26248@electric-eye.fr.zoreil.com>
I FOUND IT!!!
At least I were able to track this down very far. It seems it only appears on Port 80. So might
there be a problem if too many sockets are sharing the same port? In this case, port 80?
What can I do now? The problem is still there. All 60 seconds a break for 5 seconds. I am not really
willing to reboot anymore. So bug-hunters, please help.
Francois Romieu wrote:
> Christian Schmid <webmaster@rapidforum.com> :
>
>>I started it after one break-cyclus and stopped it immedately after the
>>next break-cyclus ended.
>
>
> I'd welcome several cycles to feed the data through gnuplot.
> A sample based on 15 minutes or more would not hurt: I speak perl too.
>
> --
> Ueimor
>
>
next prev parent reply other threads:[~2005-02-22 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 20:04 ARGH MORE BUGS!!! Christian Schmid
2005-02-21 20:19 ` Matthias-Christian Ott
2005-02-21 20:25 ` Christian Schmid
2005-02-21 20:28 ` Francois Romieu
2005-02-21 20:34 ` Christian Schmid
2005-02-21 20:56 ` Francois Romieu
2005-02-21 21:17 ` Christian Schmid
2005-02-21 21:36 ` Francois Romieu
2005-02-21 22:10 ` Christian Schmid
2005-02-21 23:03 ` Christian Schmid
2005-02-22 0:23 ` argh more bugs!!! Francois Romieu
2005-02-22 0:37 ` Christian Schmid
2005-02-22 0:10 ` Christian Schmid [this message]
2005-02-21 21:18 ` ARGH MORE BUGS!!! Christian Schmid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421A7886.8060302@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.