Hi,

On 18/02/17 08:27, Norbert Lange wrote:
> Hi,
> 
> sorry for messing up years.
> lslocks only showed makes locking /dev/null, but it appears to be that
> the culprit is a running dockerd daemon.

lslocks shouldn't be showing make holding a lock in /dev/null because it
does so for a very short period of time. It's also not in the list you
posted below.

> I dont understand why, but with the service disabled a blocked make
> will suddenly continue.

Both make and docker are locking the same file. Only one will be able to
obtain it and the other will probably hang (or fail in another way).

> to install the service:
> echo > /etc/apt/sources.list.d/docker.list 'deb [arch=amd64]
> https://apt.dockerproject.org/repo/ debian-stretch main'
> apt-get update; apt-get install docker-engine
> 
> For completeness, the lslocks output:
> $ lslocks
> COMMAND           PID   TYPE   SIZE MODE  M      START        END PATH
[...]
> dockerd          3732 OFDLCK        READ  0          0          0 /dev...

You may need to run lslocks as root to get the rest of this path.
Assuming this is a lock on /dev/null, then this is probably a bug in
docker rather than make. No-one should be holding long lived locks on
"global" files like that.

> dockerd          3732  FLOCK   128K WRITE 0          0          0
> /var/lib/docker/volumes/metadata.db

Thanks,
James

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to