Hello Jari: I have just reproduced your report issue by just similarly unquoting into my firehol.conf configuration file.
Once my firehol.conf modified, as expected, firehol try gave a similar message as the one your reported. The `try' mecanism offers the two following possibilities: 1] the try process can be stop immediately by hitting the ENTER key, and then firehol comes back to its former state; 2] you have 30 seconds to make a copy of the temporary folder created by firehol in /tmp (or $TMPDIR in the coming debian patched version) before firehol comes back to its former state. I think that 30 seconds is long enough to make a copy of the folder, and then bash debugging techniques can be used. As a matter of fact, it is not even necessary to make a copy if some basic techniques are used: at the beginning of firehol.conf you can add set -x set -v and then you can try with tee: firehol try 2>&1 | tee firehol-debug.log and hit the enter key to cancel the process; then the trace file firehol-debug.log can be analysed for debugging. More advanced bash debugging techniques that I am not aware of can certainly be used. So, I think that the `try' definitively fills well its purpose. May be the reported issue deserves some comments in README.Debian . What do you think ? Best regards, Jerome -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
