Source: suricata
Version: 3.2-1
Severity: normal

Dear Maintainer,

In #839146 you mentioned the default file is used in the init script
only. While that's certainly a position to take, the result is
on sysv systems the Suricata IDS/IDP daemon does not get started by
default, on systemd however it does. That inconsistency is
a bad idea, please fix this. In my opinino the daemon should not start
by default since it probably needs some configuration, and there
might be use cases for suricata where the daemon is not needed.

Also, after a quick glance into the init script:

| else
|     echo "/etc/default/suricata is missing... bailing out!"
| fi

No, you're not bailing out. Perhaps add "exit 0"?

    Christoph

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: unable to detect

Attachment: signature.asc
Description: Digital signature

Reply via email to