Bug#850889: suricata: Inconsistent behaviour between .init and .service

2017-05-15 Thread Arturo Borrero Gonzalez
Control: fixed -1 3.2.1-1 On Tue, 10 Jan 2017 22:11:57 +0100 Christoph Biedl wrote: > 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

Bug#850889: suricata: Inconsistent behaviour between .init and .service

2017-01-23 Thread Arturo Borrero Gonzalez
On 22 January 2017 at 23:41, Christoph Biedl wrote: > Arturo Borrero Gonzalez wrote... > >> do you have any other comment? > > I didn't get your message. Please check > https://lists.debian.org/debian-devel/2016/12/msg00613.html > So I found your answers rather by

Bug#850889: suricata: Inconsistent behaviour between .init and .service

2017-01-22 Thread Christoph Biedl
Arturo Borrero Gonzalez wrote... > do you have any other comment? I didn't get your message. Please check https://lists.debian.org/debian-devel/2016/12/msg00613.html So I found your answers rather by coincidence. > Thinking again about this, how have you find the inconsistency you are >

Bug#850889: suricata: Inconsistent behaviour between .init and .service

2017-01-20 Thread Arturo Borrero Gonzalez
On Tue, 10 Jan 2017 22:11:57 +0100 Christoph Biedl wrote: > 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

Bug#850889: suricata: Inconsistent behaviour between .init and .service

2017-01-11 Thread Arturo Borrero Gonzalez
On Tue, 10 Jan 2017 22:11:57 +0100 Christoph Biedl wrote: > 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 >

Bug#850889: suricata: Inconsistent behaviour between .init and .service

2017-01-10 Thread Christoph Biedl
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