157 reputation
117
bio website
location Italy
age 32
visits member for 5 years
seen Jun 27 '13 at 13:14

Jan
2
awarded  Popular Question
Nov
26
awarded  Famous Question
May
22
accepted Deleting a file created with a SELECT … INTO OUTFILE
Apr
4
awarded  Notable Question
Nov
24
awarded  Popular Question
Jul
28
awarded  Supporter
May
19
awarded  Popular Question
Sep
14
asked Deleting a file created with a SELECT … INTO OUTFILE
Jul
20
comment Iptables, NAT: avoiding limit on max number of requests per IP by using multiple IPs
I forgot the -j SNAT option, thanks for reminding me. I've put up the updated version of the command I'm using. Also, doing round robin on a single range of IPs is an useful suggestion, I will consider this option in the final solution. Anyway, I would still like to drop requests when the limit is reached, auto-limiting my client's ability to connect to the outside server, so my ideal situation would be a rule (or a set of rules) that match under the limit, and a final rule that matches over the limit and drops packets
Jul
20
revised Iptables, NAT: avoiding limit on max number of requests per IP by using multiple IPs
added 356 characters in body
Jul
19
revised Iptables, NAT: avoiding limit on max number of requests per IP by using multiple IPs
added 261 characters in body
Jul
19
asked Iptables, NAT: avoiding limit on max number of requests per IP by using multiple IPs
Jun
23
accepted PHP exit status 255: what does it mean?
Jun
22
awarded  Student
Jun
22
asked PHP exit status 255: what does it mean?
Mar
19
awarded  Scholar
Mar
19
accepted Lingering tcp connection in LISTEN state
Mar
18
comment Lingering tcp connection in LISTEN state
That would make sense, but I checked with pstree as you said, and it's a direct child of init not sh
Mar
18
revised Lingering tcp connection in LISTEN state
added 534 characters in body
Mar
18
comment Lingering tcp connection in LISTEN state
I'm going to try killing every process that gets ahold of the listening socket, just to see if that's the problem