argus (2:3.0.8.1-1) unstable; urgency=low

  Argus does not maintain compatibility for data files between major releases.
  The installation process for argus-server leaves existing data from previous
  packages alone (/var/log/argus/argus.log*) and logs to "argus.out" files
  instead. This both moves closer to the upstream convention and preserves
  existing data to be read by the "ra" utility from an older argus-client or
  removed as desired.

  argus startup is now managed by a systemd service rather than an init script.
  Due to a quirk in the way command line flags are handled in argus, it is
  important to ensure that /etc/argus.conf specifies ARGUS_DAEMON=no or startup 
  will likely fail. (There is no deterministic way to ensure from the command 
  line that argus starts either as a daemon or not.)

 -- Michael Stone <mstone@debian.org>  Mon, 25 Apr 2016 15:19:36 -0400