Hi,

Could you try to avoid /var/lock symlink crossing / ? It could be made a
relative symlink without policy changes and improve situation exposed in
#1039979

This will be done for forky, most probably, but I'd like to do it at
the same time as the other symlink, and also I can't do that without
looking at the consequences.

There is a potential problem in Bug #1082498, which in turn
may or may not depend on how we decide to solve #1082433 in
drbd-utils.

Ideally, I would like to see drbd-utils fixed first, if possible by
using /run/lock instead of /var/lock. This will require code changes
and someone should ensure that the package does not really need /var/lock,
but that way the existence (or not) of /var/lock will not matter so much.

Thanks.