Ensure lock file location exists

Open joe-bowman opened this issue 9 years ago • 2 comments

The supervisor init script attempts to touch the file /var/lock/subsys/supervisord without asserting that the parent folder exists, resulting in a failure to start the service.

We should ensure this folder exists as part of the salt state.

Sep 17 '16 20:09 joe-bowman

It transpires that the /var/lock/subsys appears to be a Redhat-based distro thing - hence not existing under Debian distros.

The path used probably ought to be distro specific then, rather than creating the subsys directory.

Sep 17 '16 21:09 joe-bowman

This issue is negated by #21 - #20 'fixed' the issue, but was closed because of further dependencies under Debian.

Sep 18 '16 00:09 joe-bowman