Menu

#75 --loglevel 0-2 results in error

1.0
closed
nobody
None
fixed,
2014-11-30
2014-11-28
Forage
No

The documentation states that "--loglevel" can be set from 0 to 10. However, setting "--loglevel" to either 0, 1 or 2 results in the following error:


OpenELEC:/run/lirc # lircd --driver=irtoy --nodaemon --listen --loglevel=0 --output=/run/lirc/lircd --device=/dev/ttyACM1 /storage/downloads
/lircd.conf
Bad debug level: "0"

Level could be ERROR, WARNING, NOTICE, INFO, DEBUG, TRACE, TRACE1,
TRACE2 or a number in the range 0..10.


Lirc will subsequently close again.

Using lirc 0.9.2pre1.

Discussion

  • Alec Leamas

    Alec Leamas - 2014-11-30
    • status: open --> closed
    • Resolution: na, --> fixed,
     
  • Alec Leamas

    Alec Leamas - 2014-11-30

    Provisionary release fix by updating docs in [441fc4]. A better patch might support also the "No log" level, although the usecase is hard to see. Released in 0.9.2pre2. Closing

     

    Related

    Commit: [441fc4]

  • Forage

    Forage - 2014-11-30

    The reason I ran into the issue was because I was actually trying to disable logging completely ;-)

    The use case being: making sure not even a tiny bit of resources where being put into logging.

     
  • Alec Leamas

    Alec Leamas - 2014-11-30

    I'd say that if there is a logging statement with ERROR priority which shouldn't always be visible than the priority is the bug. ERROR indicates some serious stuff which just should be fixed...

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.