python_pinger.git

@@ -10,8 +10,22 @@ process thread pings them one at a time, and prints any changes.

 ![Single Threaded Pings](http://dlma.com/images/python_pinger/ping_single_threaded.png)

-It's so simple that I'm not going to provide a sample source file,

-but for the others below, I will.

+The code for such a loop might look like this:

+

+    # results is a dict of ip_address -> last ping result

+    for address in results.keys():

+        result = ping(address)

+        if result != results[address]:

+            log(f'{time.strftime("%Y-%m-%d %H:%M:%S", now)} {address} {result}')

+            results[address] = result

+    time.sleep(delay)

+

+Logs go to a logfile, and example output looks like this:

+

+    2019-07-06 11:23:20 192.168.1.1 UP

+    2019-07-06 11:23:20 192.168.1.12 UP

+    2019-07-06 11:23:29 192.168.1.12 DOWN

+    2019-07-06 11:23:39 192.168.1.12 UP

 ### Upsides

@@ -22,7 +36,7 @@ Really simple code.

 Since the pings are serialized, one long timeout from one host could

 affect detecting a problem at another host.

-## Long Lived Workers Consuming from Queue

+## Long Lived Workers Consuming from a Queue

 Raymond Hettinger's [PyBay 2018 Keynote](https://pybay.com/site_media/slides/raymond2017-keynote/threading.html)

 uses the queue module to send data between threads, so I thought I'd make a