From: Stanislav Brabec <sbrabec@suse.cz>
To: "Trapp, Michael" <michael.trapp@sap.com>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Cc: Karel Zak <kzak@redhat.com>
Subject: Re: libuuid related tasks for next v2.39
Date: Mon, 11 Apr 2022 15:45:52 +0200 [thread overview]
Message-ID: <7609d7ad-b9fb-7977-8f22-3bdef2b2c950@suse.cz> (raw)
In-Reply-To: <AM9PR02MB70447FD1C9D326ABAF7ABFE8F9E69@AM9PR02MB7044.eurprd02.prod.outlook.com>
Dne 07. 04. 22 v 10:23 Trapp, Michael napsal(a):
> For uuidd this would result in:
> -no need for a lock on LIBUUID_CLOCK_FILE, what also might help to
> solve some authorization issues.
This should be a benefit.
The only possible downside would be losing of context on uuidd restart.
That happens e. g. during a security update.Could this be a problem?
Really fast machines restart in a small fraction of second.
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: sbrabec@suse.com
Křižíkova 148/34 (Corso IIa) tel: +420 284 084 060
186 00 Praha 8-Karlín fax: +420 284 084 001
Czech Republic http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76
next prev parent reply other threads:[~2022-04-11 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:21 libuuid related tasks for next v2.39 Karel Zak
2022-04-11 13:36 ` Stanislav Brabec
2022-04-12 11:36 ` Karel Zak
[not found] ` <AM9PR02MB70447FD1C9D326ABAF7ABFE8F9E69@AM9PR02MB7044.eurprd02.prod.outlook.com>
2022-04-11 13:45 ` Stanislav Brabec [this message]
[not found] ` <CAA0A08XAF2eWScVKQ1Jd0vUPfHzZw8PAtiS-jRbom0EvRQ+Zsg@mail.gmail.com>
2022-04-12 10:34 ` Karel Zak
[not found] ` <CAA0A08VmzKTzFCEqnFP9tw50zgx4iPsif_BktuRSAvfm3hH52w@mail.gmail.com>
2022-04-12 11:44 ` 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=7609d7ad-b9fb-7977-8f22-3bdef2b2c950@suse.cz \
--to=sbrabec@suse.cz \
--cc=kzak@redhat.com \
--cc=michael.trapp@sap.com \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).