XigmaNAS

Hi,
Sorry for my english language, I'm french man and everyone knows we aren't good for Shakespeare language.
I write in english forum because I have no answer in french forum.

So, in the log system, I see all the messages.
In particular, 90 % of messages concern problems of "transmission-daemon" of the bittorrent service.
It is also necessary to sort out to find messages more typed "system".
We can find messages "transmission-daemon" in the filter for log "daemons", and I think it would be better not to have them in the option "System", no?
Because for any little on a file torrent, it generates a repetitive message in the log "System" with title "transmission-daemon".
Someone has a solution so that this messages "transmission-daemon" do not put always in messages Systems, because it makes difficult the legibility of the log system which interests me most.
There is well a solution to extract the log and to leak out to eliminate messages "transmission-daemon", but I must make it for every visit of the log, pfffff!
Have you an idea?

Thanks.

Did someone have a solution ? I have the same issue.

Why not an option in BitTorrent service ?

You can add in "Extra options" -e --logfile where logfile=path to your separate log file.
Check https://www.freebsd.org/cgi/man.cgi?que ... .0-RELEASE

That way it will log to separate log not the system one.

Thanks
But the note for extra options speaks about transmission remote, not transmission daemon, and e option doesn't have the same action. Am I wrong ?

You are right, sorry for the confusion...
I will try to think of something different.

Well, just a shortcut I tested now, not a solution..

From the ssh. service transmission stop
Edit settings.json file and change "message-level": 2, to "message-level": 0, save the file (tools/edit file menu in the webui).
Then enter by ssh to the machine and write, service transmission start (enter)
By using it the settings.json file is not overwritten and then the changes will be permanent even after new software upgrade.

Cheers

Victek wrote: ↑

25 Mar 2017 20:07

Well, just a shortcut I tested now, not a solution..

From the ssh. service transmission stop
Edit settings.json file and change "message-level": 2, to "message-level": 0, save the file (tools/edit file menu in the webui).
Then enter by ssh to the machine and write, service transmission start (enter)
By using it the settings.json file is not overwritten and then the changes will be permanent even after new software upgrade.

Cheers

The users of the the Great Wall blockade from China say you are doing so well. Finally solve the problem in the log to the system