Description:

The writing of the PID in /etc/rc.d/metalog is broken in two ways:

1) $PID is used to write the file, but $PID is only set BEFORE starting metalog to get the pid of an instance that might already be running.
After starting metalog, $PID is not set again, but just written to the pid-file. So usually this results in an 'echo "" > /var/run/metalog.pid'
2) metalog has a pid-file-handling of its own. If no other parameter is set, uses the same path as the init-script. So metalog and the init-script race for writing this file.

I've restarted metalog a few times and seen both possible errors: an empty file and a broken file (empty line and a few digits of the correct pid)

Additional info:
* version 2.0-1

Steps to reproduce:
* start metalog and check /var/run/metalog.pid and compare to the pid of the metalog-master process (because there is a race involved, it might be fine sometimes)

Possible fix:
As metalog writes a pid-file itself, a fix is pretty simple: stop writing the pid-file from the init script.