Re: [RFC PATCH] libuuid: introduce safe variant of uuid_generate_time()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 28, 2011 at 06:10:40PM +0100, David Sterba wrote:
> On Friday 28 January 2011 16:26:59 Davidlohr Bueso wrote:
> > Both of these make a lot of sense.
> >
> > > * loop until daemon socket is available, always returning a uuid
> > > alothough it may take unspecified time
> >
> > Not too sure about this one.
> 
> quoting from Karel's mail:
> 
> > > int uuid_generate_time_nf(uuid_t out)     /* nf = "no fallback" */
> > what about uuid_generate_safe_time(uuid_t out) ?
> 
> this would fulfill the "_safe_" meaning from such an API function and I think 
> it makes sense to have something like "give me an UUID whatever it takes".

David, I'm not sure I understand what you mean: do you suggest to
change the semantics of *_nf()/*_safe_time() to "wait arbitrarily
long until the daemon could be connected ~> the UUID is safe" ?

Petr

--
Petr Uzel
IRC: ptr_uzl @ freenode

Attachment: pgpUIeUJ0JKeO.pgp
Description: PGP signature


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux