Yes, this is an old bug. :)
If anyone is interested, here's my own solution to this problem; the
idea is simply to add some randomness to the interval between locking
attempts.
In my experience with a 4-in-1 device, the first interval is scattered
enough for all attempts to go through on the
Hello again,
I was pondering a lock-less solution and your patches seem to provide a
good upgrade path towards that. Unfortunately:
$ git clone git://git.katzien.de/usbmount.git
Cloning into usbmount...
git.katzien.de[0: 82.165.99.49]: errno=Connection timed out
fatal: unable to
Package: usbmount
Severity: normal
Hello,
I tested Jan's patch with a flash drive that has 12 partitions on it.
The original position of the locking code just at the beginning of the
add handler will usually only be able to mount 3 to 4 partitions on my
machine before lockfile-create will give
Package: usbmount
Severity: normal
Hello Jan,
I have just looked at #403209 and the patch proposed there seems to me
to lead straight into race conditions upon finding a free mount point
(see there for further reference).
The problem you described sounds almost as if you had the #403209-patch
Hi,
Unfortunately I'm currently without the usbmount using box, so I can't
test anything.
In git.katzien.de/usbmount.git (only available via git, not via
webinterface) are my latest attempts to fix some bugs in and add some
features to usbmount. This three commits may help with that
5 matches
Mail list logo
