124 reputation
5
bio website
location
age
visits member for 3 years, 1 month
seen Aug 21 at 1:11

Feb
24
awarded  Popular Question
Feb
25
accepted Where can be stored MySQL data directory?
Feb
23
awarded  Commentator
Feb
23
comment Where can be stored MySQL data directory?
@Jay: There are different pieces of software or APIs that have some restrictions (to be same partition, etc.) and probably the reasons are subtile. Well, if MySQL has no such restriction, this is a good news, thanks. BTW, is this subject described somewhere in the official docs?
Feb
23
asked Where can be stored MySQL data directory?
Feb
16
accepted Using WITH_FAST_MUTEXES configure option when building MySQL 5.5
Feb
15
comment Using WITH_FAST_MUTEXES configure option when building MySQL 5.5
So, shortly one could say: WITH_FAST_MUTEXES is a valid option, but missing from docs (probably without intention); by default it's OFF and can be enabled; it's performance impact is negligible in the vast majority of the cases; it could help just in some edge situations, but also be harmful in others.
Feb
15
revised Using WITH_FAST_MUTEXES configure option when building MySQL 5.5
deleted 2 characters in body
Feb
15
asked Using WITH_FAST_MUTEXES configure option when building MySQL 5.5
Feb
7
accepted slow iptables listing after adding a DROP rule
Feb
6
comment slow iptables listing after adding a DROP rule
Thanks. Yes, REPLY packets, this is definetly the point that skipped to me. Probably it would be useful to mention these details in your answer, so others serching for this subject could read it there and not in comments. Now all the pieces of the puzzle fell into place.
Feb
6
comment slow iptables listing after adding a DROP rule
But I'm dropping packets of the INPUT chain, i.e. coming from outside world to the PC. Or do I get wrongly this point of the filter:INPUT chain?
Feb
6
comment slow iptables listing after adding a DROP rule
Sorry, but probably you got wrongly the focus of the question. As I wrote above, I know that -n will speed up the -L command, but the question is why a DROP rule triggers it. It would be logically to get this slowness just after adding the first rule because even the first ACCEPT should process the packets. And also the difference between 0.0.168.192.in-addr.arpa and 192.168.0.0 is strange for me.
Feb
5
comment slow iptables listing after adding a DROP rule
@mgorven: I've mentioned about this Q. I'm not asking how to make it quick, but why a DROP rule triggers this slowness while the previous rule that specifies the IP deosn't. It would be logically to have this effect after adding just the first rule.
Feb
5
revised slow iptables listing after adding a DROP rule
added 214 characters in body
Feb
5
asked slow iptables listing after adding a DROP rule
Feb
5
awarded  Scholar
Feb
5
accepted iptables “host/network not found” with an exclamation mark IP address
Feb
4
answered Configure IPTABLES to MASQUERADE traffic from a single host in lan and block other
Feb
4
awarded  Editor