Difference between revisions of "Monitoring TCPSER for activity"

From Jay's Cafe' Wiki
(Created page with " *Trial #1<p /> Hypothesis: If I can identify traffic FROM the VICE client, then I can restart the system when the traffic has stopped over an hour.<p /> [https://www.cyberci...")
 
m
 
Line 1: Line 1:


*Trial #1<p />
'Experiment #1<p />
Hypothesis: If I can identify traffic FROM the VICE client, then I can restart the system  
Hypothesis: If I can identify traffic FROM the VICE client, then I can restart the system  
when the traffic has stopped over an hour.<p />
when the traffic has stopped over an hour.<p />
[https://www.cyberciti.biz/faq/how-do-i-check-if-a-port-is-in-use-on-linux/ Resource Doc #1]
[https://www.cyberciti.biz/faq/how-do-i-check-if-a-port-is-in-use-on-linux/ Resource Doc #1]
'Experiment #2<p />
Hypothesis: Monitor the logs from tcpser -L 7 or the lowest setting that has the "SEND" data stream identified in the comments.
<p />
*Method:
**set tcpser -v 25232 -I -l 7 -L ~/.logs/tcpser.log
**parse the logs every ''x'' minutes to determine whether a restart is necessary.

Latest revision as of 07:17, 20 February 2022

'Experiment #1

Hypothesis: If I can identify traffic FROM the VICE client, then I can restart the system when the traffic has stopped over an hour.

Resource Doc #1 'Experiment #2

Hypothesis: Monitor the logs from tcpser -L 7 or the lowest setting that has the "SEND" data stream identified in the comments.

  • Method:
    • set tcpser -v 25232 -I -l 7 -L ~/.logs/tcpser.log
    • parse the logs every x minutes to determine whether a restart is necessary.