log file

[GoogleCodeExporter]

We need a log file for SAM output, so the output doesn't just go to the console 
window (or goes to log file instead).

Original issue reported on code.google.com by meeshmu...@gmail.com on 2 Mar 2013 at 1:28

[GoogleCodeExporter]

Thoughts:
1) Should there be a log file for clients also?

2) Where should the log file(s) live?  In the directory SAM was run from, or in 
/var/log or elsewhere?

3) Should the SAM log file grow indefinitely or be erased/started fresh with 
each run of SAM? 

4) In the case of clients, there can be multiple instances running on the same 
machine, so should they all write to the same log file?  They would need unique 
identifiers (pid?).

5) Log files for debugging can grow quite fast, if a message is printed at 
every audio tick.  If there is one central SAM log file for routine messages 
(start/stop/register/unregister etc.) then perhaps there should be a separate 
debug file?

6) The log file writing needs to be done on its own thread so we don't block 
the audio thread with file I/O.

Original comment by meeshmu...@gmail.com on 6 Mar 2013 at 10:31

[GoogleCodeExporter]

1) yes, a log file per client would be nice. if you could title the log file 
with the name/descriptor of the client & date that would be useful.
2) i would create a folder for the logs in the root SAM directory
3) i would rotate SAM log files for a week with one day per file
4) each client should have it's own log
5) i would have just one SAM log file for debugging & routine messages. perhaps 
somewhere in a config file users could specify the verbosity
6) agreed logging should run in a saperate thread

Original comment by tma...@gmail.com on 8 Mar 2013 at 2:53

[GoogleCodeExporter]

tr

Original comment by tangdanh...@gmail.com on 24 Oct 2014 at 12:04