Linux: Use config file for gateway settings

[marceloaqno]

• The following settings can be use on the config file:
  • verbose=[debug,info,notice,warn,err] - Logging verbosity. Default=debug
  • log_file=[0|1] - Enable logging to a file. Default=0
  • log_filepath=[/tmp/mysgw.log] - Log file path.
  • log_pipe=[0|1] - Enable logging to a named pipe(aka fifo). Default=0
    Use this option to view your gateway's log messages from the
    log_pipe_file (defined below).
    To do so, run the following command on another terminal:
    • $ cat "log_pipe_file"
  • log_pipe_file=[/tmp/mysgw.pipe]
  • syslog=[0|1] - Enable logging to syslog. Default=0
  • eeprom_file=[/etc/mysensors.eeprom]
  • eeprom_size=[1024]
• Change some mysgw parameters:
  • Added:
    • -q, --quiet: for quiet mode, disable log messages written to the
      terminal.
  • Removed:
    • -d, --debug: removed, log messages are now enabled by default.
  • Replaced:
    • -b, --background: replaced by --daemon
• isatty() is no longer used, log messages by default are printed to
  stderr unless the gateway is started with --quiet (Option to disable isatty check for Linux gateway #1022)
• MY_LINUX_CONFIG_FILE: no longer holds the path to the eeprom file,
  but to the configuration file

[mfalkvidd]

We'll need to document the possible config file settings and their default values, preferably in Doxygen. Perhaps an activity for the Hackathon?

Edit: the config file setting will automatically be documented since it is mentioned in ./configure --help. So no need to document it separately. Just add it to the blacklist in keywords.txt in the Raspberry Pi gateway section.

[mfalkvidd]

We'll need to update the build page with these changes when doing the release.