You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: