linuxdcpp-team team mailing list archive

[Steven Sheehy <steven.sheehy@xxxxxxxxx>]

Public bug reported:

It would be useful to diagnose user's issues to log the raw NMDC command
to the hub's log file. This is already done for ADC with the ADC_DEBUG
setting. If this is done for NMDC as well should we combine this into
one setting since it doesn't really make sense to have a separate
preference to log NMDC and ADC separately?

Or even better, instead of making a debug setting specific to one or two
areas why not add log levels to LogManager? This way we can just send
everything to the LogManager at debug level and the LogManager will
decide whether to append it to the logs based on its configured level.

Regardless of which approach, should it log to hub chat like adc does?
I'm not too keen on cluttering the gui with information that is readily
available in the log and can be followed with tail -f.  Thoughts?

** Affects: dcplusplus
     Importance: Wishlist
         Status: New


** Tags: core log nmdc

-- 
Log raw NMDC commands
https://bugs.launchpad.net/bugs/549372
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.

Status in DC++: New

Bug description:
It would be useful to diagnose user's issues to log the raw NMDC command to the hub's log file. This is already done for ADC with the ADC_DEBUG setting. If this is done for NMDC as well should we combine this into one setting since it doesn't really make sense to have a separate preference to log NMDC and ADC separately?

Or even better, instead of making a debug setting specific to one or two areas why not add log levels to LogManager? This way we can just send everything to the LogManager at debug level and the LogManager will decide whether to append it to the logs based on its configured level.

Regardless of which approach, should it log to hub chat like adc does? I'm not too keen on cluttering the gui with information that is readily available in the log and can be followed with tail -f.  Thoughts?