ccloli / teamviewer-incoming-recorder Goto Github PK

On Linux, TeamViewer saves its log at /var/log/teamviewer12/${env.USER}/TeamViewer12_Logfile.log, but incoming log file is at /var/log/teamviewer12/Connections_incoming.txt.

As Node.js doesn't support watching subdirectory on Linux, possibly we should watch the two files separately. So --TeamViewerDir maybe useless, we should set full path on --logFileName and --incomingFileName.

The recording with tv 14 is not working. Maybe the logfiles has changed.

If TeamViewer doesn't run as service, and have multiple incoming connections, once one of them disconnected, FFmpeg will stop recording immediately, since the connection has been written to Connections_incoming.txt. However, the other connection is still connecting, and the latter actions and new incoming connection won't be recorded until all the connections are closed, because TeamViewer doesn't need to open a new TeamViewerDesktop task.

It's a good way to listen to the TeamViewerDesktop task, checking if it has closed. If yes, stop recording and renaming it as incoming logs. If no, continue recording until it closed, then write all connections log to filename, like 20170305144001-20170305144111-123456789(foo)-987654321(bar)-741852963(baz).mp4.

In TeamViewer12_Logfile.log, once TeamViewerDesktop task started, there will be a log says like TeamViewerDesktop started, PID=3080, so that we can use a timer to check if that process stopped. On Windows, we can use tasklist /fi "pid eq 3080" | find "3080" to check if the process still exists. If exists, it will returns the details of the task; if not, it will returns an empty string.