Hi Jerome,
On Sat, Nov 23, 2019 at 10:54:29AM +0400, Jerome BENOIT wrote:
> On 18/11/2019 21:39, Toni Mueller wrote:
> > My patch in Salsa may not yet be quite functional, but it changes the
> > 'firehol' script itself to read /etc/default/firehol and then exit if
> > this variable is not set to
Hello Toni,
On 18/11/2019 21:39, Toni Mueller wrote:
>
> Hi Jerome,
>
> making the systemd unit file read /etc/default/firehol would not change
> a thing because there is no logic available to act upon the
> START_FIREHOL variable.
>
> My patch in Salsa may not yet be quite functional, but it c
Hello,
On 18/11/2019 23:03, Michael Norton wrote:
> The only dilemma is that I do not know if there is some Debian policy around
> how (1) is supposed to be handled. I will try to look into it.
This looks as an Init Systems issue. So, for now, I do not expect a clear
answer.
Jerome
--
Jero
Oh, so apparently there is a patch… somewhere?
But is there actually any reason to keep the /etc/default/firehol file and the
START_FIREHOL logic? I don’t understand the point of having it. What would be
wrong with “systemctl [enable/disable] firehol”? That would be more proper, no?
AFAIK files
Hi Jerome,
making the systemd unit file read /etc/default/firehol would not change
a thing because there is no logic available to act upon the
START_FIREHOL variable.
My patch in Salsa may not yet be quite functional, but it changes the
'firehol' script itself to read /etc/default/firehol and t
5 matches
Mail list logo
