Most of the time, the logging process keeps the log open, accesses it via
a file descriptor and gets notified of log rotation via a signal. Because
logrotate does not wait that the log is close (could it do it with inotify ?),
there can be race conditions between the compression and events that are logged
at the same time.

In the case of NEO, logs are SQLite DB. Rotation is also notified via a signal
and VACUUM is sometimes called to reduce its size.

Otherwise, stable eggs may be used.

This reverts commit 9a3dcc60.

Conflicts:

	software/slaprunner/common.cfg

  The branch erp5testnode should not be a dependency for install a release.

Parameter names are more generic.

It doesn't work yet with erp5testnode and conflicts with resiliency tests.

  * Copy Re6st logs if exist.
  * Include smartmontools, lm-sensors, rrdtools
  * Implement smartmontools logging
  * Implement network benchmark monitoring

i.e returns parameters.