On Mon, Jun 20, 2022 at 05:10:36PM +0200, Michael Trapp wrote:
> In a uuidd setup, the daemon is a singleton and can maintain it's own
> resources for time based UUID generation. This requires a dedicated
> 'clock sequence range' but does not need any further lock/update of
> the LIBUUID_CLOCK_FILE from uuidd. The range of available clock values
> is extended by a continuous handling of the clock updates - instead of
> updating the value to the current timestamp, it is incremented by
> the number of requested UUIDs.
> ---
>
> Updated version
> cont clock handling needs to be activated with '-C' or '--cont-clock'.
> default value of max_clock_offset is 7200 seconds.
> custom value of max_clock_offset can be defined by optional argument.
> maximum value of max_clock_offest is 365 days.
Looks good, thanks! I'll apply the patch later this week.
BTW, by the reset interval is 7200 seconds? Why not 3600? :-)
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
