Improving logging of install.sh script

[pgrenaud]

I would like to follow up on issue #907.

While I was working on the PRs I submitted last week, the lack of output from the install.sh script made debugging really hard. At some point I ended up removing all &>/dev/null from the install.sh script, which allowed me to actually debug and fix the issues.

Looking at the commit history, there use to be options ($DEBUG_STD and $DEBUG_ERROR) that allowed to redirect the output to a file. But those were replaced by &>/dev/null at some point and I don't understand why. Could you explain the reasoning behind this decision?

@six2dez I would like to submit a PR to address this issue. I was thinking of redirecting the output of the commands to a log file, the same way that reconftw.sh outputs to $LOGFILE. Would that be an acceptable solution to you?

[six2dez]

Hi! Thanks again for all the PR's <3

tl;dr yes sure :)

---

In the reconftw.cfg file there are these lines that are intended to allow debugging of the installer. The idea is that if you need to debug the installer, you can just leave it with an empty value:

reconftw/reconftw.cfg

Lines 41 to 42 in eafc131

	DEBUG_STD="&>/dev/null" # Skips STD output on installer
	DEBUG_ERROR="2>/dev/null" # Skips ERR output on installer

I have tried several times to implement a "verbose" flag in reconftw.sh, but I have not been able to implement it in a good way without breaking everything:

• A log file
• Keep a clean output
• Give the option to print everything

That long story aside, yes, you can implement the log file for the installer :)

[pgrenaud]

Ok, thanks for your input. I'll take a look at that next time I can free some time at work.