https://bugs.kde.org/show_bug.cgi?id=408547
--- Comment #6 from Chris E <iherm...@yahoo.com> --- (In reply to Chris E from comment #5) > (In reply to Milian Wolff from comment #1) > > odd, that's EAGAIN which isn't documented as a possible return value in > > https://linux.die.net/man/2/flock > > > > but as the error indicates, we should probably just try again? I'll try to > > write a patch eventually, but can't promise an ETA since I'm quite busy - so > > if you can reproduce it, try to wrap the flock in a loop that checks for > > EAGAIN? > > Code should check for EWOULDBLOCK which is in the flock manual page list of > returns: > On many systems there are similar defines to this one: > /usr/include/asm-generic/errno.h:#define EWOULDBLOCK EAGAIN /* > Operation would block */ > The question of course becomes who has the file locked such that LOCK_NB is > causing the EWOULDBLOCK ? whoops should have read PR first. smells like a bug in flock to me -- You are receiving this mail because: You are watching all bug changes.
