Util-Linux package development
 help / color / mirror / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: Chris Hofstaedtler <zeha@debian.org>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] libuuid: Move clock.txt to /run
Date: Wed, 1 Mar 2023 15:26:04 +0100	[thread overview]
Message-ID: <20230301142604.GA19419@kitsune.suse.cz> (raw)
In-Reply-To: <20230301141747.jpbvk4aieq3pdehh@zeha.at>

On Wed, Mar 01, 2023 at 03:17:47PM +0100, Chris Hofstaedtler wrote:
> * Michal Suchanek <msuchanek@suse.de> [230301 15:10]:
> > Moving the clock.txt to /run which is in tmpfs should resolve the
> > problem even for users not running uuidd.
> [..]
> >  
> > -#define LIBUUID_CLOCK_FILE	"/var/lib/libuuid/clock.txt"
> > +#define LIBUUID_CLOCK_FILE	"/run/libuuid/clock.txt"
> 
> Last time I asked about this file on this mailing list, I was
> informed that clock.txt is supposed to survive reboots.
> Moving it to /run (or any other tmpfs) would break this.

What's so valuable in it that it needs to survive?

I don't have it at all.

Also the code seems to re-synchronize with the real time clock from time
to time which makes the content relevant only for limited periods of
time.

Thanks

Michal

  reply	other threads:[~2023-03-01 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 14:09 [PATCH] libuuid: Move clock.txt to /run Michal Suchanek
2023-03-01 14:17 ` Chris Hofstaedtler
2023-03-01 14:26   ` Michal Suchánek [this message]
2023-03-01 16:49     ` Theodore Ts'o
2023-03-01 17:17       ` Michal Suchánek
2023-03-01 18:39         ` Theodore Ts'o
2023-03-01 20:08           ` Michal Suchánek
2023-03-01 17:54 ` Karel Zak

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=20230301142604.GA19419@kitsune.suse.cz \
    --to=msuchanek@suse.de \
    --cc=util-linux@vger.kernel.org \
    --cc=zeha@debian.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