aMule Forum
English => Feature requests => Topic started by: vdb on July 31, 2005, 12:36:43 PM
-
I've been using the amule daemon for a while now, and I am very happy with it. However, I do miss the logging capabilities that the amule GUI offers: Banned users, start/finish of hashing new files, connection attempts to servers etc. All I now see is "started amuled".
Would it be possible to extend the logging of the daemon in a next release?
-
You have exactly same log in amuled as with gui amule. There's option to put all the log to stdout (-o if I remember correctly). It will not work, however if you detached daemon from controlling tty (with --full-daemon for example).
There's some issue with log not being flushed while amuled is running, and this is to be fixed.
-
Ah, yes, that is what I do, run it with the -f option to have it detached so I can run it as a service from a startup script at boot time.
So my real question would then be: Can the logging be improved so that when using it as a detached daemon the logs will still be as complete as with the GUI or the non-detached amuled?
-
Can the logging be improved
Can, and will.
-
Thanks! Will be looking forward to this!
-
Well, most people don't like daemons/sevices messing up their screen with messages (if at all it is possible). However, the log is always there, despite that you can't see it. You can check it with the webserver, or by looking at the contents of ~/.aMule/logfile
-
Not if you run it detached, the total content of my logfile is:
2005-08-01 21:49:21: Credit file loaded, 14142 clients are known
2005-08-01 21:49:21: Loaded ipfilter with 0 new IP addresses.
C'est tout.
As you can see there are no logs when you run it detached. If you can help me with a startup script that will run it from rc5.d at boot time, while still retaining the total log capability, please give me a hint. I tried some things, but it seems that only the "amuled -f" will really start from a startup script, otherwise it just keeps waiting for some input. Or I must be doing something wrong, in which case I am very open to help on this. :) (Oh btw, the "screen" command is not something I would like to start from the init scripts....)
-
The logs are there. they're just not flushed.