From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <66b68380.16.mr2ice.fgrirsq@earthlink.net>
Date: Fri, 09 Aug 2024 14:00:48 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-10530152@2rosenthals.com>
Subject: Re: [eCS-ISP] help about an Injoy FW rule

In <list-10530152@2rosenthals.com>, on 08/09/24
   at 02:44 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi Massimo,

>> i've created a ticket:
>> 
>> https://github.com/bitwiseworks/InJoy/issues/78

>update

>if i copy and paste 100% of the content of the include rule file
>"spam.cnf" in firerule.cnf, i don't get the issue

>now i've a huge firerule file..
>firerule.cnf	 323.988

>it's unreadable :-)
>but it works

That's odd.  It implies some sort of problem parsing the #include
statement, but I can't see anything obvious.

If you want anyone to be able to help you with this, you are probably
going to have to provide them a copy of your ruleset.

Refresh my memory a bit.  IIRC, you have been using #include to import
rules for a long time and it's only relatively recently when the .cnf
files got a bit larger that the failures began?  True?

It should not matter, but what type of line endings do your .cnf files
have?  The pristine .cn_ files have unix line endings, but the working
.cnf files have DOS line endings and do not end with a Ctrl-Z.

Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------