Hi,
At Tue, 16 Dec 2008 17:39:11 +0100,
Stefan Fritsch wrote:
>
> Package: cowdancer
> Version: 0.44
Why is this so old?
> Severity: normal
>
> When several cowbuilder instances are started in parallel, dpkg/aptitude
> in each instance will try to lock its lock file. However, since the
> files are linked across chroots, only the first succeeds and all other
> fail with
>
> Could not get lock /var/lib/dpkg/lock - open (11 Resource
> temporarily unavailable)
>
> The strace output is
> fcntl64(4, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) =
> -1 EAGAIN (Resource temporarily unavailable)
>
> As a workaround, it seems to be possible to do
>
> rm /var/cache/pbuilder/base.cow/var/lib/dpkg/lock
> rm /var/cache/pbuilder/base.cow/var/lock/aptitude
>
> But it would be better if cowdancer would implicitly copy a file if
> a process in the chroot tries to lock it.
I've noticed that too.
What's the lock function they use?
regards,
junichi
--
dan...@{netfort.gr.jp,debian.org}
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
