bakker_be wrote:
> Try as I might, I can't seem to redirect the DEBUG output to a file.
> AFAIK "./music-similarity.py -l DEBUG > musicsimilarity.log" should send
> all output to the musicsimilarity.log file. It does create the file, but
> all other output remains in the terminal window :(
Try:
Code:
--------------------
./music-similarity.py -l DEBUG 2>&1 | tee musicsimilarity.log
--------------------
'2>&1' ensures standard-error messages are placed on the same output as
standard-output. '|' pipes the output of the left hand side to the right
hand side. 'tee' takes this and shows on terminal and places into
'musicsimilarity.log'
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http: //SERVER:9000/material/?debug=json,cometd to also see update
messages, e.g. play queue) 2. Open browser's developer tools 3. Open
console tab in developer tools 4. REQ/RESP messages sent to/from LMS
will be logged here.
------------------------------------------------------------------------
cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686
View this thread: http://forums.slimdevices.com/showthread.php?t=115609
_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
