0000912: amuled logging capabilities

(0002026)
Kry (manager)
2006-06-10 17:15

It does write to ~/.aMule/logfile

(0002032)
EvaSDK (reporter)
2006-06-13 19:51

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

(0002034)
JusTiCe8 (reporter)
2006-06-15 10:53

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.

(0002035)
pcmaster (reporter)
2006-06-17 23:35

amuled creates an empty file (0 bytes) in /var/log/amuled.log

(0002841)
pcmaster (reporter)
2008-06-29 09:42

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.

Issue History
Date Modified	Username	Field	Change
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

Notes
(0002026) Kry (manager) 2006-06-10 17:15	It does write to ~/.aMule/logfile

(0002032) EvaSDK (reporter) 2006-06-13 19:51	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

(0002034) JusTiCe8 (reporter) 2006-06-15 10:53	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.

(0002035) pcmaster (reporter) 2006-06-17 23:35	amuled creates an empty file (0 bytes) in /var/log/amuled.log

(0002841) pcmaster (reporter) 2008-06-29 09:42	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.

Relationships