fix screen command logging option

[behrisch]

fixes raspbian compatibility

[sylvandb]

The problem is multiple versions of screen and this fix may not be sufficient.

Try screen --version to see the version of screen you have and man screen to see if your version supports -Logfile or if it supports a filename following the -L option. You can also try: screen --help | grep -- -L

The versions I have (not a complete list!):

4.02 does not support a filename following -L, and this fix causes screen to attempt to execute the log filename instead of the next command: -L Turn on output logging.

4.05 does support -L filename -- probably the version this pull request was developed: -L [file] Turn on output logging. Set logfile name.

4.06 does support the -Logfile filename option: -L Turn on output logging. -Logfile file Set logfile name.

[behrisch]

Even if it not solves everything, it is better than before, especially since the c't article mentions raspbian as supported.

[behrisch]

According to the change log the option was added in 4.5.0 so I tried to fix the script according to that but I could not test it.

[drushbrook]

Apart from losing the named session capability - what else would we lose if we dropped screen and used nohup and backgrounded processes?

Given none of the things that run in the screen session require input we still can monitor the processes by redirecting stdout / stderr to a file?

[behrisch]

@drushbrook I would very much prefer not to use screen but I suppose there was a reason to do it that way (which I do not know).

[merlinschumacher]

I plan to move the entire process to a single python script in the near future, thus rendering the screen issue moot.

[kueblc]

I plan to move the entire process to a single python script in the near future, thus rendering the screen issue moot.

If you do this, please keep entry points for each process. These scripts may be independently useful in doing things other than flashing! 😄

[sylvandb]

It would be nice in a single python script, if it were import'able and (at least) the former separate scripts were separately callable functions.