I tried upgrading pip when prompted to do so: sudo pip install –upgrade pip This worked, but removed the system install in /usr/bin/pip and replaced it with /usr/local/bin/pip – NOT GOOD! The solution is as follows:
All credit to Matt Wilcox for this excellent article, for which this post is based – thank you, Matt! https://mattwilcox.net/web-development/unexpected-ddos-blocking-china-with-ipset-and-iptables/ All commands run as root!
1
2
3
4
yum install-yipset
vi blockchina(see below forcontents)
chmod755blockchina
./blockchina
Do this once only:
1
iptables-AINPUT-ptcp-mset--match-set china src-jDROP;service iptables save
Then add blockchina to the root cron
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
#!/bin/sh
#
# blockchina
#
DIR=/etc
# Create the ipset list
ipset-Nchina hash:net
# remove any old list that might exist from previous runs of this script
Step 1. Execute the following two commands: postconf -e smtpd_sender_restrictions=pcre:/etc/postfix/rejected_domains postconf -e reject_unauth_destinations=pcre:/etc/postfix/rejected_domains If that doesn’t work, you may hand-edit main.cf and add/edit these lines:
Upgraded the OS on one of my Amazon server instances today. After rebooting I had the unpleasant experience of seeing my rpc.rstatd monitoring daemon stop functioning. It turns out that AWS changed the actual kernel version for this release, I guess to “celebrate” the fact that it is no longer “beta”. The difficulty is that […]
http://code.google.com/p/s3fs/wiki/FuseOverAmazon The s3fs password file has this format (use this format if you have only one set of credentials): accessKeyId:secretAccessKey If have more than one set of credentials, then you can have default credentials as specified above, but this syntax will be recognized as well: bucketName:accessKeyId:secretAccessKey