| MarkH_UK | SHA-2? lol |
| Brandano | Perfectly fine with me as long as someone else does the hard work |
| action | niq upgrades encryption to ROT26 |
| niq | upgrades encryption to ROT26 |
| DrBacchus | Twice as secure as ROT13 |
| gryzor | that would make a nice changelog |
| yango | there are lots of implementations of SHA256, brandano so the hard work is done |
| Brandano | with an option for cereal packet decoder ring? |
| ALVAN | hi all |
| fajita | All is not in today, ALVAN |
| ALVAN | i got a question ..how can i found out why i have so many CLOSE_WAIT processes |
| Brandano | I wonder what she will say the day All is in |
| All | hi all |
| fajita | All is not in today, All |
| DrBacchus | Now you know |
| ALVAN | i got 941 CLSOE_WAIT apche processes i is this ..and they never die |
| DrBacchus | ALVAN: Someone is attempting to DOS you, and you might want to block them at the firewall. |
| ALVAN | until the pache server is maxxet out |
| niq | keepalivetimeout |
| fajita | keepalivetimeout is http://httpd.apache.org/docs-2.0/mod/core.html#keepalivetimeout |
| ALVAN | i set keepalive timeout to 120 |
| niq | far too long! |
| ALVAN | o timeout is set to 120 sory keep alive timeout is 0 |
| DrBacchus | Well, there you go solution? |
| fajita | Solution: Don't do that. |
| Brandano | That onlycovers about 60% of all known problems |
| ALVAN | KeepAliveTimeout 0 |
| Brandano | another 35% is covered by saying "Don't do that" to the programmer |
| ALVAN | so where is the problem? |
| DrBacchus | You have timeout set to 120 Which explicitly says, keep "CLOSE_WAIT" threads open for 2 minutes. So it is obediently doing what you just asked about. |
| thumbs | 15 or 30 seconds might scale better |
| niq | still too long |
| yango | 0.01 seconds |
| niq | 3 seconds should be ample |