Fix command-line parsing of loggingPath
Fix command-line parsing of loggingPath

The "-l" option for loggingPath was not enabling logging when given,
as it should have been. Now, logging can be enabled either by use of
command line or by existence of sentinel file, as intended.

Thanks to Anton Kachalov and Konstantin Klubnichkin for catching this
bug.

Also cleaned up the printing of the informational lines printed, for
loggingEnabled and tuningEnabled, to be correct as originally
intended: printed when enabled, no output when disabled.

Signed-off-by: Josh Lehan <640cdef0d88764f22de94dce2c05fc22b037d36b@google.com>
Change-Id: I3f20a4dee997e04985d32cd6020b719e0b4d117e

openbmc/phosphor-pid-control,openbmc/phosphor-pid-control