Most people doing threading in Python know about Python's GlobalInterpreter Lock (GIL), which causes only one thread to be running inthe CPython interpreter at any one time. This means that threadedcode already has a certain amount of implicit locking going on,making certain operations thread-atomic without you writing explicitlocks.

The important thing about the GIL for this is that it protectsbytecodes, not Python statements . If something happens in a singlebytecode, it's protected; otherwise, you need explicit locking

Presented once again in illustration:

; sdig ns isotech.com.cydns2.lordosinfo.com.dns1.lordosinfo.com.; sdig ns lordosinfo.com.dns1.edynet.com.cy.dns1.lordosinfo.com.; sdig ns edynet.com.cy.dns2.netconnect.com.cy.dns1.netconnect.com.cy.

At the moment:

• dns2.netconnect.com.cy is not responding,
• dns1.edynet.com

This week we received 20,583 email messages from 213 different IPaddresses. Our SMTP server handled 21,213 sessions from 1,044different IP addresses. This is a significant jump in incoming emailcompared to last week .

We saw a major jump in connections compared to last week :238,300 connections from at least 32,400 different IP addresses.Broken down by day, it goes:

Presented in illustrations:

; dig +short ns harvest.idv.tw.harvest.idv.tw.www.harvest.idv.tw.; dig +short a harvest.idv.tw.219.84.30.59; dig +short a www.harvest.idv.tw.219.84.30.59

To those setting up nameservers: when people said 'have twonameservers', they did not mean 'and feel free

Today's examples of MX entries are all drawn from domains presented toour mailer in MAIL FROM 's over the past 28 days or so. ' sdig ' is ascript that does a ' dig +short '. Presented in illustrated form:

; sdig mx oakhavenresort.com.10 mail.10 mail.oakhavenresort.com.

It's interesting that they get this simultaneously wrong and right. Isthe plain ' mail. ' supposed to be in some other domain?

; sdig mx