All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Jan Remmet <J.Remmet@phytec.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rootfs-postcommands: generate /var/lib/systemd/clock
Date: Wed, 15 Jun 2016 12:14:17 -0700	[thread overview]
Message-ID: <7E603C53-3E9F-488E-8AC2-AA8D4AB8DBC0@gmail.com> (raw)
In-Reply-To: <1465997797-6613-1-git-send-email-j.remmet@phytec.de>

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]


> On Jun 15, 2016, at 6:36 AM, Jan Remmet <J.Remmet@phytec.de> wrote:
> 
> systemd timesyncd check /var/lib/systemd/clock instead of
> /etc/timestamp.
> If this file is missing it defaults to TIME_EPOCH. It's set while
> configuring systemd.
> 
> Signed-off-by: Jan Remmet <j.remmet@phytec.de>
> ---
> meta/classes/rootfs-postcommands.bbclass | 6 ++++++
> 1 file changed, 6 insertions(+)
> 
> diff --git a/meta/classes/rootfs-postcommands.bbclass b/meta/classes/rootfs-postcommands.bbclass
> index db8b551..0c7b764 100644
> --- a/meta/classes/rootfs-postcommands.bbclass
> +++ b/meta/classes/rootfs-postcommands.bbclass
> @@ -234,6 +234,12 @@ python write_image_manifest () {
> # sane default time setting
> rootfs_update_timestamp () {
> 	date -u +%4Y%2m%2d%2H%2M%2S >${IMAGE_ROOTFS}/etc/timestamp
> +
> +	if ${@bb.utils.contains("DISTRO_FEATURES", "systemd", "true", "false", d)}; then
> +		# touch needs timestamp as [[CC]YY]MMDDhhmm[.ss]
> +		TS=$(sed 's/[.]*/&./13' ${IMAGE_ROOTFS}/etc/timestamp)
> +		touch -t $TS ${IMAGE_ROOTFS}/var/lib/systemd/clock
> +	fi
> }

i wonder if this will work with read only rootfs.

> 
> # Prevent X from being started
> --
> 1.9.1
> 
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2016-06-15 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 13:36 [PATCH] rootfs-postcommands: generate /var/lib/systemd/clock Jan Remmet
2016-06-15 19:14 ` Khem Raj [this message]
2016-06-16 14:17   ` Jan Remmet
     [not found]   ` <5762b536.ea7ec20a.4591c.ffffbfc2SMTPIN_ADDED_BROKEN@mx.google.com>
2016-06-16 14:38     ` Khem Raj
2016-06-16 14:57       ` Peter Kjellerstedt
  -- strict thread matches above, loose matches on Subject: below --
2016-06-15  9:23 Jan Remmet
2016-06-15 10:02 ` Martin Jansa
2016-06-15 13:31   ` Jan Remmet

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=7E603C53-3E9F-488E-8AC2-AA8D4AB8DBC0@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=J.Remmet@phytec.de \
    --cc=openembedded-core@lists.openembedded.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.