Support for LSBs /run in the RAs

Hi!

LSB specification recently introduced /run as storage for run-time information with the idea to have it available as soon as possible in the boot process(as /var could be separate FS mounted later). At least Debian implements /run as tmpfs, which means that you can't rely on the presence of any sub-directories there.

There are at least several RAs which expect to find their PID files and other run-time information in the subdirectories of the [/var]/run. Obviously they fail on new Debian(and Ubuntu, I guess).

Those have to be fixed by checking the existence of the PID directory and creation of it if necessary.

Affected RAs at least named(#350), zabbixserver, mysql, mysql-proxy and lxc.

apache2, seems, has a cure for it, although I haven't checked(Could have permissions problems).

With regards,
Timur Bakeyev.

Inspect the named RAs—#350, zabbixserver, mysql, mysql-proxy, and lxc—for PID and runtime subdirectory handling. Start by checking how each agent uses /var/run or /run; done means the affected agents create missing PID directories and work when /run is a fresh tmpfs, with apache2 considered for comparison.

Written by the indexing model from the issue text.