Package: open-vm-tools Version: 2:10.1.0-4449150-1 Severity: minor Dear maintainer,
starting with upstream version 10.1.0-4449150 (at least this is the upstream version in https://github.com/bzed/pkg-open-vm-tools/tree/master/open-vm-tools/udev) open-vm-tools now ship an udev rule setting the timeout by itself. This leads to two udev rules doing the same, with the upstream rule matching a superset of ATTRS. ==> 60-open-vm-tools.rules <== # VMware SCSI devices Timeout adjustment # # Modify the timeout value for VMware SCSI devices so that # in the event of a failover, we don't time out. # See Bug 271286 for more information. ACTION=="add|change", SUBSYSTEMS=="scsi", ATTRS{vendor}=="VMware " , ATTRS{model}=="Virtual disk ", RUN+="/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'" # VMWare Virtual Sockets permissions ==> 99-vmware-scsi-udev.rules <== ACTION=="add", SUBSYSTEMS=="scsi", ATTRS{vendor}=="VMware*" , ATTRS{model}=="Virtual disk*", RUN+="/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'" ACTION=="add", SUBSYSTEMS=="scsi", ATTRS{vendor}=="VMware*" , ATTRS{model}=="VMware Virtual S", RUN+="/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'" We noticed that because our local system management sets this to a different value in a rule that gets sorted before 99-vmware-scsi-udev. I propose to drop the Debian specific rule and install the upstream one at the previous location (with priority < 99 to be able to override if necessary). Bernhard
