Comment 25 for bug 1870087

Hi Mark and anyone affected. Just to clarify the remaining part of the issue:

From the various test scenarios which I have tried, the initial issue of the client failing to restart in the presence of stale lock files and sockets appears to be resolved. That is, lock files pointing to dead or recycled PIDs should not prevent client starting if the client is in fact not running. This can be verified by checking processes matching PIDs are not landscape:

  ls -l /var/lib/landscape/client/sockets/*.sock.lock
  readlink -v /var/lib/landscape/client/sockets/*.sock.lock | xargs ps

However, there is an issue of processes not cleaning their lock/sock at exit. This issue affects all currently supported releases (as far as 16.04) and should be addressed in an upcoming patch.