Where is Transmission-Qt Logfile?
Where is Transmission-Qt Logfile?
I just built transmission-qt version 2.50 in debian, but i cannot figure out how to view or specify a logfile. The message-level is set to 3 in settings.json. There is nothing in the manual or --help regarding logs, nor anything in the GUI that i could find.
Otherwise everything works great.
Otherwise everything works great.
Re: Where is Transmission-Qt Logfile?
It logs to /var/log/messages.
The only other option I can think of is when I run it under the debugger, then I get the log on the terminal. Now that I think about that, there's also an environment variable to redirect the log... TR_DEBUG_FD which needs a number (stdin = 0, stdout = 1, stderr = 2) and allows you to redirect the output to a file... there's also TR_CURL_VERBOSE, and TR_DHT_VERBOSE.
The only other option I can think of is when I run it under the debugger, then I get the log on the terminal. Now that I think about that, there's also an environment variable to redirect the log... TR_DEBUG_FD which needs a number (stdin = 0, stdout = 1, stderr = 2) and allows you to redirect the output to a file... there's also TR_CURL_VERBOSE, and TR_DHT_VERBOSE.
Re: Where is Transmission-Qt Logfile?
yes i previously had checked there and /var/log/syslog , and just now tried changing permissions to 666 but still nothing is showing up in those logs. as you mentioned this works..rb07 wrote:It logs to /var/log/messages
TR_DEBUG_FD=1 transmission-qt >./qt.log
but the logfile contains far too much detail and it grows about 100KB per minute in size .. it's overkill for my purposes.
I will just have to assume that important errors or warnings will show up somewhere in the GUI, at least i hope so.
Re: Where is Transmission-Qt Logfile?
will do that.gunzip wrote:message-level is set to 3
Yep, when things start turning red...gunzip wrote:I will just have to assume that important errors or warnings will show up somewhere in the GUI
Re: Where is Transmission-Qt Logfile?
reducing message-level to 1 didn't seem to change anything with respect to TR_DEBUG_FD=1, it still is overkill.
OK thanks, so far i'm lucky as the interface remains a nice shade of blue ..rb07 wrote:Yep, when things start turning red...
Re: Where is Transmission-Qt Logfile?
I was wondering what does the "Message Log" menu option on the Desktop notification area icon is supposed to do. Mine does nothing, and the option only appears there.
Re: Where is Transmission-Qt Logfile?
cool i didn't even realize that was there, but i get same result as you: nothing happens. the other menu options in the notifications seem to work, but not the Message Log thing.rb07 wrote:I was wondering what does the "Message Log" menu option on the Desktop notification area icon is supposed to do. Mine does nothing, and the option only appears there.
come to think about it, the daemon, gtk and mac versions all have user-friendly logfiles, but not qt. i'm new to qt so don't know if this is a regression or something that never got developed in the first place.
Re: Where is Transmission-Qt Logfile?
I just checked the code, and its the later, never got developed.
The code uses a non implemented action, qt/mainwin.cc:
The code uses a non implemented action, qt/mainwin.cc:
Code: Select all
menu->addAction( ui.action_ShowMessageLog );
Re: Where is Transmission-Qt Logfile?
Very good, you solved the mystery.
Then this could be made into an enhancement ticket (if it's not there already), but i think the developers have enough on their plate at the moment.
Then this could be made into an enhancement ticket (if it's not there already), but i think the developers have enough on their plate at the moment.
Re: Where is Transmission-Qt Logfile?
I don't have coding skills to do any patch, but i just found this open ticketx190 wrote:Yeah, but when are they going to dig in?But then again, if you were to submit a patch...
Add "Message Log" support to Qt client
it's 2 years old with not much happening in recent times.
Re: Where is Transmission-Qt Logfile?
There is a log for transmission-qt now !
See ticket #3212, there's a new patch (thanks to Koboneil) I just started testing, not bad for a first version.
See ticket #3212, there's a new patch (thanks to Koboneil) I just started testing, not bad for a first version.