Follow-up Comment #3, bug #67726 (group make):

[comment #2 comment #2:]
>> For some work we're doing [2][3], we're emulating a FIFO using CUSE/FUSE to
>> allow tracking when consumers disappear to avoid lost tokens.
> 
> 
> This is one of those good intentions that has the potential to cause trouble,
> because this feature lets the other side to not track their tokens. Which
> locks the the other side to your jobserver and a specific file type and
> hinders interoperability.
> 

We're diagnosing it when it happens, though. Otherwise you have no idea who
ate the tokens.

> 
>> After you open the FIFO and consume the token, do not close it until after
>> you've written the token back
> 
> A program that is coded to return the tokens, will not at the same time be
> coded to close the fifo prematurely, right?

No, I think we saw a project that does return it, it just doesn't keep the
fifo open the whole time.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?67726>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to