From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] initscripts: fix timestamp check at bootmisc.sh
Date: Tue, 13 Dec 2011 12:26:53 +0000 [thread overview]
Message-ID: <1323779213.2731.63.camel@ted> (raw)
In-Reply-To: <1323759539-23945-1-git-send-email-lauri.hintsala@bluegiga.com>
On Tue, 2011-12-13 at 08:58 +0200, Lauri Hintsala wrote:
> Timestamp checking has been broken by the commit
> 2078af333d704fd894a2dedbc19cef5775cdadbb. Fix timestamp checking
> and clean the code.
>
> cc: sgw@linux.intel.com
> cc: gary@mlbassoc.com
>
> Signed-off-by: Lauri Hintsala <lauri.hintsala@bluegiga.com>
> ---
> .../initscripts/initscripts-1.0/bootmisc.sh | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh b/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh
> index 03fd67c..6d68b35 100755
> --- a/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh
> +++ b/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh
> @@ -62,16 +62,16 @@ then
> fi
>
> # Set the system clock from hardware clock
> -# If the timestamp is 1 day or more recent than the current time,
> +# If the timestamp is more recent than the current time,
> # use the timestamp instead.
> /etc/init.d/hwclock.sh start
> if test -e /etc/timestamp
> then
> - SYSTEMDATE=`date -u +%2m%2d%2H%2M%4Y`
> - read TIMESTAMP < /etc/timestamp
> - NEEDUPDATE=`expr \( $TIMESTAMP \> $SYSTEMDATE + 10000 \)`
> - if [ $NEEDUPDATE -eq 1 ]; then
> - date -u $TIMESTAMP
> + SYSTEMDATE=`date -u +%4Y%2m%2d`
> + TIMESTAMP=`cat /etc/timestamp | awk '{ print substr($0,9,4) substr($0,1,4); }'`
> + NEEDUPDATE=`expr \( $TIMESTAMP \> $SYSTEMDATE \)`
> + if [ $NEEDUPDATE -eq 1 ]; then
> + date -u `cat /etc/timestamp`
> /etc/init.d/hwclock.sh stop
> fi
> fi
For reference, the code in the boot process is trying not to cause
fork/exec calls. This is why it does:
read TIMESTAMP < /etc/timestamp
since this is faster than forking to run cat. Could we fix this in a
different way to avoid the fork/execs?
I appreciate this is a small detail but over the whole boot process it
mounts up!
Cheers,
Richard
next prev parent reply other threads:[~2011-12-13 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 7:07 [PATCH] initscripts: fix timestamp check at bootmisc.sh Lauri Hintsala
2011-12-13 6:58 ` [PATCH v2] " Lauri Hintsala
2011-12-13 7:45 ` Koen Kooi
2011-12-13 8:26 ` Lauri Hintsala
2011-12-13 12:26 ` Richard Purdie [this message]
2011-12-13 12:36 ` Phil Blundell
2011-12-13 12:58 ` Lauri Hintsala
2011-12-13 13:07 ` Phil Blundell
2011-12-13 13:18 ` Lauri Hintsala
2011-12-13 13:24 ` Phil Blundell
2011-12-13 13:31 ` Henning Heinold
2011-12-13 13:40 ` Lauri Hintsala
2011-12-14 6:27 ` [PATCH v3] initscripts: fix timestamp checking " Lauri Hintsala
2011-12-15 19:17 ` Saul Wold
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=1323779213.2731.63.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox