From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 14610091 for ecs-isp@2rosenthals.com; Sun, 26 Oct 2025 21:00:35 -0400 Received: from [192.168.200.201] (port=53323 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.98.2) (envelope-from ) id 1vDBb4-000000005bi-1Mfs for ecs-isp@2rosenthals.com; Sun, 26 Oct 2025 21:00:30 -0400 Received: from mta-201a.earthlink-vadesecure.net ([51.81.229.180]:34415) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1vDBb2-0000000087T-1Hhf for ecs-isp@2rosenthals.com; Sun, 26 Oct 2025 21:00:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=CpCnBGcPWLvxW38XJOOHlUiEyUxuQjBGqVbMLY yyoQo=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1761526827; x=1762131627; b=RTIC20i3Pq/xLy/bL6z3xhY4Q81 uHJp4ssMGEc1w4tKuxZvk/4mJ/jm79GA0pkBoIAakga7J+YgSmtFd80mlCVojw/UmFLGwGl yllhXEN/g2wAAUIJNpmpdVLcmkSJivD1aLe5kS9c5VyTEHZ4yml1BchfXVH9fK2lM2/pnp6 oFnykBb/v+J1ZifS06B6+2uBrRjuIDIfInjTbItD0XfEe2haUbWh6jds26UZPIeQVjWY7VN I60M11dhkpgwCUCocVkWIQGqoFxaBBWkdmX9gCkeWkQxiQVzv92YO8skb40dtinEDUSwcij 3bantiiWjyAOPy8EUlidSICJ16010rg== Received: from slamain ([107.202.224.188]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id 5b63546c-18723350f40c4d9a; Mon, 27 Oct 2025 01:00:27 +0000 Message-ID: <68fecb81.43.mr2ice.fgrirsq@earthlink.net> Date: Sun, 26 Oct 2025 17:31:45 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Os2_ntpD issue X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 10/26/25 at 10:46 PM, "Massimo S." said: Hi Massimo, >os2_ntpd 193.204.114.105 2 3 You may not have let os2_ntpd run long enough. What happens if you run os2_ntpd as os2_ntpd 193.204.114.105 2 0 os2_ntpd like most ntp clients is intended to run as a daemon and implements a protocol that typically only makes small changes to the clock time and once the clock error is determined can keep the clock time correct for a long time without an internet connection. Daytime is different. Daytime jam sets the clock based on what the daytime server returns which little regard for server response time, intermittent errors and such. It's good enough for the needs of most OS/2 users, but there's a reason NTP is the standard on most platforms. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------