README.Gentoo documenting differences to stock behaviour

README.Gentoo (text/plain), 1.69 KB, created by Michael Weiser on 2016-11-13 19:28:55 UTC

The MailScanner installed by this package differs from stock behaviour in the
following ways:

- We're not using ms-init for starting the daemon. Instead we rely on standard
  openrc behaviour. systemd is not currently supported (explicitly, i.e. by a
  service unit).

- We do not need /var/lock/subsys/MailScanner for anything so we don't create
  it.

- But we do create MailScanner.off to signify that MailScanner has been stopped
  intentionally since this is used by scripts such as ms-check. But we do so in
  /run instead of /var/lock/subsys.

- /etc/MailScanner/defaults is not used. Instead there is a
  /etc/conf.d/MailScanner derived from it, containing only those settings which
  are actually used.

- Most notably there's no run_mailscanner setting that needs to be set to 1 in
  order for MailScanner to be started. Instead just do an

  # rc-update add MailScanner
  # service MailScanner start

  as usual.

- ms-check will restart the daemon if /run/MailScanner.off does not exist, a
  PID file exists but no process matching it. This should catch cases where the
  daemon has crashed badly and needs restarting. It does not need to be enabled
  using setting run_mailscanner in /etc/MailScanner/defaults.

  Stock ms-check would also start the daemon if the PID file was missing. To
  guard against accidentally starting the daemon from an ms-check cron job some
  time after installation but before configuration is finished it only does
  anything when run_mailscanner is enabled in /etc/MailScanner/defaults. This
  could still get awkward when installing the package, starting to configure it
  (including the run_mailscanner setting) and ms-check is run from its cron job
  before configuration is finished.