All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathanael Noblet <nathanael-sGhsi8tFlmY@public.gmane.org>
To: Rex Vaughn <rvaughn-6nyMWi6rSIjR7s880joybQ@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ntpd to set clock prior to mount
Date: Thu, 14 Nov 2013 20:48:13 -0700	[thread overview]
Message-ID: <5285997D.5090005@gnat.ca> (raw)
In-Reply-To: <CAF-o458j3=kA8FWMLzg9VSg-Pg5SrOjzPY4sN64U9kZv0i-j7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11/14/2013 04:23 PM, Rex Vaughn wrote:
> I have a set of machines that don't have battery backups for the real
> time clock. when the power is cycled on these machines, the real time
> clock resets to the BIOS epoch time which is usually a year or two in
> the past.  Each time I boot, I get fsck failure because the superblock
> time is in the future.  I am aware of the e2fsck configuration file
> that I can put into /etc with the broken_clock option, however I
> still get log files that have the time set in the past.  Having
> invalid times in the log files can make debugging boot problems very
> problematic.
>
> I have hacked together a dracut ntpd module that will set the time but
> it requires modifications to the network module to turn on the network
> even when netroot is not set.
So I'm looking at writing a module that requires network access but does 
not require netroot, so I'd be interested in any improvements to the 
network module that allowed for early networks.

  parent reply	other threads:[~2013-11-15  3:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 23:23 ntpd to set clock prior to mount Rex Vaughn
     [not found] ` <CAF-o458j3=kA8FWMLzg9VSg-Pg5SrOjzPY4sN64U9kZv0i-j7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-15  3:48   ` Nathanael Noblet [this message]
     [not found]     ` <5285997D.5090005-sGhsi8tFlmY@public.gmane.org>
2013-11-15 14:52       ` Rex Vaughn
2013-11-15 13:28   ` Colin Guthrie
2013-11-15 15:49     ` Rex Vaughn

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=5285997D.5090005@gnat.ca \
    --to=nathanael-sghsi8tflmy@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rvaughn-6nyMWi6rSIjR7s880joybQ@public.gmane.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.