linuxdcpp-team team mailing list archive

[DjSlash <907372@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

There's always a logfile created in '$configdir/logs/', even with a
different logfile location defined in the config. This logfile only
contains 'Core initialized' entries so far. The point of having a
logfile location definition in the config is that you can find your
logfiles where you expect them. If the daemon is logging in different
locations, it's easy to oversee messages that might be usefull (when the
core doesn't honor the definition, what else doesn't?).

** Affects: adchpp
     Importance: Undecided
         Status: New


** Tags: config logfile

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/907372

Title:
  Always a logfile in configdir/logs

Status in ADCH++:
  New

Bug description:
  There's always a logfile created in '$configdir/logs/', even with a
  different logfile location defined in the config. This logfile only
  contains 'Core initialized' entries so far. The point of having a
  logfile location definition in the config is that you can find your
  logfiles where you expect them. If the daemon is logging in different
  locations, it's easy to oversee messages that might be usefull (when
  the core doesn't honor the definition, what else doesn't?).

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/907372/+subscriptions