-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Quick question: can anyone remember the reason why all the config files end in ''#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE'' or something similar? I''m starting work on a shorewall preprocessor that will allow multiple firewalls to be administered from a single system (not a GUI, though), and i''m trying to work out whether i need to put the last line tags in the configs i generate. Thanks, Paul http://paulgear.webhop.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+vN9Q0yv0OWRYqWwRAjIDAJ4mfXVxMFKIyCNbPEBbFW04hbNGzACfWvnY 3gAsn8MvlSjvdLciBbtS0Rc=JmaT -----END PGP SIGNATURE-----
> Quick question: can anyone remember the reason why all the config files > end in ''#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE'' > or something similar?The last uncommented line should end in a new line character, ''#LAST LINE...'' ensures it. Nerijus
On Sat, 2003-05-10 at 04:15, Paul Gear wrote:> > Quick question: can anyone remember the reason why all the config files > end in ''#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE'' > or something similar? > > I''m starting work on a shorewall preprocessor that will allow multiple > firewalls to be administered from a single system (not a GUI, though), > and i''m trying to work out whether i need to put the last line tags in > the configs i generate. >Paul, The shell ''read'' command ignores the last line if it is not terminated by a linefeed character. Keeping that comment on the last line of every config file that is processed using ''read'' insures the last line of real data will be properly terminated. Saves a lot of "I added ... to my ... file and Shorewall is ignoring it" reports... -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net