Timeline for How to determine the status of my server
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2016 at 21:27 | comment | added | user1133275 | @Storo if whatever service is providing the telnet or HTTP dies nmap will report the port not open, so unless you are checking for a responsive but otherwise broken service there is no need to use curl/telnet, but even if there were replacing nmap with curl/telnet would still be lighter than presence.py. | |
| Oct 13, 2016 at 20:47 | review | Low quality posts | |||
| Oct 14, 2016 at 0:11 | |||||
| Oct 13, 2016 at 20:43 | comment | added | Centimane | @Storo even if it's purpose is not the port specifically it's not inappropriate for them to suggest that a lighter application would be the best course of action. Have you also considered reversing the relationship for presence.py? (Each node reports their status to the server with a timestamp, offloading much of the CPU work to the clients.) | |
| Oct 13, 2016 at 20:38 | comment | added | Storo | Sorry but this question has nothing to do with replacing the Presence service. So your solution is off topic. Your code has nothing to do with what that service does. I quote: "Each thread checks the status of its node via telnet or HTTP once per second, so you can imagine the load of each process." Clearly it has nothing to do with a port. | |
| Oct 13, 2016 at 20:28 | history | edited | user1133275 | CC BY-SA 3.0 | added 109 characters in body |
| Oct 13, 2016 at 20:21 | history | edited | user1133275 | CC BY-SA 3.0 | added 129 characters in body |
| Oct 13, 2016 at 20:15 | history | answered | user1133275 | CC BY-SA 3.0 |