From: Po Lu <luangruo@yahoo.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Bruno Haible" <bruno@clisp.org>,
"Robert Pluim" <rpluim@gmail.com>,
bug-gnulib@gnu.org, "Pádraig Brady" <P@draigbrady.com>,
"Sven Joachim" <svenjoac@gmx.de>,
64937@debbugs.gnu.org, "Natanael Copa" <natanael.copa@gmail.com>,
Emacs-devel@gnu.org, "Thorsten Kukuk" <kukuk@suse.com>
Subject: Re: boot time on Linux
Date: Thu, 10 Aug 2023 14:58:44 +0800 [thread overview]
Message-ID: <87bkfftmcb.fsf@yahoo.com> (raw)
In-Reply-To: <e88700f4-8631-1910-46b2-c344366ffbd8@cs.ucla.edu> (Paul Eggert's message of "Wed, 9 Aug 2023 23:22:17 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 2023-08-09 19:14, Po Lu wrote:
>> This uses the uptime counter (which also results in an SELinux denial
>> for me, but different Android distributions have SELinux policies of
>> varying strictness), which cannot establish the precise time the system
>> started
>
> Emacs doesn't need a precise boot time. All it really needs is an
> integer that uniquely identifies the current OS boot.
>
>> since time elapses between the read from the uptime counter and
>> the read from the RTC.
>
> Emacs allows for up to one second of slop in computing the boot
> time. (In other words, it assumes that reboots are at least one second
> apart.) So if there are minor errors in computing the boot time it
> should be OK. If the errors are greater than one second, though,
> lock-file may assume that locks are stale when they're not.
OK, but the SELinux problem still stands in the way. There's an uptime
counter in the Settings app though -- I'll try to establish how that
works.
next prev parent reply other threads:[~2023-08-10 6:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tttmpt5h.fsf@turtle.gmx.de>
[not found] ` <20230808173430.GA27131@suse.com>
[not found] ` <26226778.6c9BZvbsD2@nimes>
[not found] ` <3732835.vtg8X0x55z@nimes>
2023-08-09 19:31 ` boot time on Linux Paul Eggert
2023-08-09 21:06 ` Bruno Haible
2023-08-09 23:53 ` Po Lu
2023-08-10 0:14 ` Bruno Haible
2023-08-10 2:14 ` Po Lu
2023-08-10 6:22 ` Paul Eggert
2023-08-10 6:58 ` Po Lu [this message]
2023-08-10 10:30 ` Bruno Haible
2023-08-10 12:23 ` bug#64937: " Po Lu via GNU coreutils Bug Reports
2023-08-10 12:25 ` Bruno Haible
2023-08-10 13:04 ` Po Lu
2023-08-10 14:12 ` Bruno Haible
2023-08-11 8:27 ` Po Lu
2023-08-10 9:30 ` Natanael Copa
2023-08-10 9:38 ` Po Lu
2023-08-10 10:05 ` Natanael Copa
2023-08-10 15:30 ` Bruno Haible
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkfftmcb.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=64937@debbugs.gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=P@draigbrady.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=kukuk@suse.com \
--cc=natanael.copa@gmail.com \
--cc=rpluim@gmail.com \
--cc=svenjoac@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).