|Anonymous | Login | Signup for a new account||2023-09-26 23:36 CEST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000912||aMule||Feature Request||public||2006-06-10 07:52||2008-07-21 17:50|
|Target Version||Fixed in Version|
|Summary||0000912: amuled logging capabilities|
|Description||amuled should be able to write a logfile to somehere else than stdout or /dev/null.|
If in a good mood, why not implementing it using syslog ?
|Tags||No tags attached.|
|Fixed in Revision|
|It does write to ~/.aMule/logfile|
I was thinking of being able to specify another place for this via the config file or a command line option.
This would be pratical for moving this file to an appropriate file, for example /var/log/amuled.log
Also, amule core logfile managment have to be improved cause now, if logfile is truncated externally, amule is lost and don't log anything more.
I suggest in log procedure to check if logfile is still opened, in other case: reopen a new one, and continue logging.
Also, amuled could be aware of SIGHUP to re-read its config.
|amuled creates an empty file (0 bytes) in /var/log/amuled.log|
Same issue in 2.2.1: when amuled starts, it creates a new log file in ~/.aMule/logfile, renaming the old logfile to ~/.aMule/logfile.bak.
This is not a problem, but when starts, amuled also creates an log file in /var/log/amuled.log. This file is empty (0 bytes long) and amuled never write anything to it.
|2006-06-10 07:52||EvaSDK||New Issue|
|2006-06-10 07:52||EvaSDK||Operating System||=> Any|
|2006-06-10 17:15||Kry||Note Added: 0002026|
|2006-06-13 19:51||EvaSDK||Note Added: 0002032|
|2006-06-15 10:53||JusTiCe8||Note Added: 0002034|
|2006-06-17 23:35||pcmaster||Note Added: 0002035|
|2008-06-29 09:42||pcmaster||Note Added: 0002841|
|2008-07-21 17:50||Wuischke||Status||new => acknowledged|
|Copyright © 2000 - 2023 MantisBT Team|