From: Klaus Dittrich <kladit@arcor.de>
To: Valdis.Kletnieks@vt.edu
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rc* / xinetd
Date: Thu, 13 Oct 2005 09:02:35 +0200 [thread overview]
Message-ID: <434E068B.1060607@arcor.de> (raw)
In-Reply-To: <200510122013.j9CKDVGV032270@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Wed, 12 Oct 2005 20:27:00 +0200, Klaus Dittrich said:
>
>
>
>>service time
>>{
>> type = INTERNAL
>> id = dgram_time
>>
>>
>
>That, my friends, is UDP port 37, not UDP port 123 where NTP lives.
>
>
>
The time requester is a router. I looked up
it's configuration and indeed TIME/UDP is the
protocol used.
You are right, I mixed up ntp with time. Sorry.
So, the corretced message is ..
I noticed a huge cpu usage of xinetd with 2.6.14-rc4
starting with the first time/udp request.
I will try older rc's today to narrow the point in time
this problem started.
--
Klaus
next prev parent reply other threads:[~2005-10-13 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 14:36 2.6.14-rc* / xinetd Klaus Dittrich
2005-10-12 17:45 ` Valdis.Kletnieks
2005-10-12 18:27 ` Klaus Dittrich
2005-10-12 20:13 ` Valdis.Kletnieks
2005-10-13 7:02 ` Klaus Dittrich [this message]
2005-10-13 11:08 ` Klaus Dittrich
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=434E068B.1060607@arcor.de \
--to=kladit@arcor.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/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.