From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C18E713838B for ; Tue, 30 Sep 2014 13:15:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A2CD1E0B2F; Tue, 30 Sep 2014 13:15:01 +0000 (UTC) Received: from mail-qg0-f48.google.com (mail-qg0-f48.google.com [209.85.192.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7B4C8E0B01 for ; Tue, 30 Sep 2014 13:15:00 +0000 (UTC) Received: by mail-qg0-f48.google.com with SMTP id i50so3294644qgf.7 for ; Tue, 30 Sep 2014 06:14:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HeICUVxseQiQ3L6EtDdVk22VjS5wlPd/JRN3F3h4134=; b=yIq9RRezxW+/PqmzH91+c168EoXwy7u/zjBw23E0qFSIYKUDjV4mT2JqPALIalnOV+ duFqlgF8RXKBh3YbrYLacXJgy7Zx10UZA9V2/WuDSAtngQahQcQa2QBATyAOvUzOe6ip faxEzD5dOy1VI0ZuUL6FJe82DKeETMhRDde04c1tK+U8y30ix3Y+YaMIvwKE5UJrl41e Furmb1YZG5u8hIQGLF1c5dAO6rR0PWIHkq+MzjeHvCrzdnvjkPBttcPko1ZmczJA74UT fIZbEV8BmDkFDZUQ3oQ8o8ZdQuUiSkC20etahi+/qaSydW6sT9mv+LaQCwkqRCr2psBG ETxg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.140.19.36 with SMTP id 33mr70223681qgg.32.1412082899669; Tue, 30 Sep 2014 06:14:59 -0700 (PDT) Received: by 10.224.113.16 with HTTP; Tue, 30 Sep 2014 06:14:59 -0700 (PDT) In-Reply-To: <20140930123428.GG3828@solfire> References: <20140930101234.GC3828@solfire> <201409301122.09391.michaelkintzios@gmail.com> <542A85DB.9040500@thegeezer.net> <20140930103906.GD3828@solfire> <20140930114323.4f267030@digimed.co.uk> <20140930114944.GF3828@solfire> <20140930123428.GG3828@solfire> Date: Tue, 30 Sep 2014 09:14:59 -0400 Message-ID: Subject: Re: [gentoo-user] Re: another "headless device"-question: In search of the LAN From: "Poison BL." To: gentoo-user Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: d2c9898d-a4eb-46bc-8917-4a0dc5bcd65e X-Archives-Hash: b35fe543dec3aa22e7a9d7e829ad9c2a On Tue, Sep 30, 2014 at 8:34 AM, wrote: > James [14-09-30 14:24]: >> Meino, >> >> >> Make sure your system time (hwclock) is properly set upon bootup. >> Since you are running on an embedded hardware board, I'd look at >> those docs and find a forum as to the specifics of how the hardware >> clock is set and maintained on the board. Once you get it close, >> then ntp should be configuration. >> >> man hwclock >> >> hth, >> James >> >> > > Hi James, > > ...the system has no built-in RTC which still runs if the system is > powered off. > After power is up and eth0 is alive, the time/date has to be set via > ntp-client. The rest already working. > I called > /etc/init.d/ntp-client start > after booting the little beast and plugging in the RJ45 and everything > else was fine. > Currently I am experimenting with chrony (emerging). > Will see, if this will make a difference ;) > > Best > mcc > The trick for bringing the clock into the right era after boot on a system like that one (and what's used in raspbian for the pi) is to, at shutdown, write the current date/time into a file. Then, on boot, set the date/time to what that file has, meaning it won't be perfectly accurate, but it will be considerably closer until ntp's available to it again. The most important thing that accomplishes for me is, while it doesn't keep the wall clock times accurate, maintaining the right order of times on log messages, etc. It also prevents a lot of issues with log and backup rotations that depend on 'which file is newer?', etc. -- Poison [BLX] Joshua M. Murphy