lkml.org 
[lkml]   [2005]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.14-rc* / xinetd
    Valdis.Kletnieks@vt.edu wrote:

    >On Wed, 12 Oct 2005 16:36:57 +0200, Klaus Dittrich said:
    >
    >
    >>I noticed a huge cpu usage of xinetd with 2.6.14-rc4
    >>starting with the first ntp request.
    >>
    >>
    >
    >Umm.. why is xinetd listening for ntp requests at all? I'm pretty sure that
    >xinetd fighting with xntpd for control of the socket isn't going to work nicely,
    >although I admit being mystified as to (a) why this ever worked for you and
    >(b) what specifically changed in -rc4 to cause the CPU spin.
    >
    >What was the most recent kernel known to work, and what does the xinetd
    >config file entry for NTP look like
    >
    >

    2.6.13.3 works. I can compile an try 2.6.14-rc[1,2,3].

    service time
    {
    type = INTERNAL
    id = dgram_time
    socket_type = dgram
    protocol = udp
    user = root
    wait = yes
    only_from = 192.168.168.36 192.168.168.39
    }


    This setup worked for years now. The machine
    (192.168.168.32) is the time-server and I have
    chosen this setup to simulate and verify a real
    world scenario.

    /etc/ntpd.conf
    ..
    driftfile /etc/ntp.drift
    logfile /var/log/ntp
    #authenticate no
    server 127.127.8.0 prefer mode 2 # Meinberg ANZ_14 (Standart Telegramm)
    server 127.127.1.1 # Local clock in case of disaster
    fudge 127.127.1.1 stratum 10 # Poor stratum for local clock
    --
    Klaus

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-10-12 20:32    [W:0.094 / U:0.056 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site