ispcp-apache logger was rewritten. i'll commit later. The problem will be fixed.
About the problem (subject of this thread), if you have not the same problem with the update script, it's not a sleep statement that must be added. With this last information, we can now inspect correctly (lock issue).
Note: The limit 1024 can be changed.
And please Daniel you know me so, calm down. I don't understand why your are nervous. I've proposed you IRC session but you didn't answer.
No pm activated so:
sci2tech by PM Wrote:Never received any invitation to discuss anything from nobody. And I`m not nervous, my english is even worse because I stopped using since 1 year, and this maybe make you / anybody else believe that I`m nervous . But I dislike to see that every action I take is seen as provocation or some flame try. Was just a simple error report, and as soon a I opened that ticket my trac account stopped to work, that’s why I used forum. My mistake it seems. Anyway just for the record that limit can be changed with ulimit (kind of tricky) or recompiling apache. I did used both, and you can see this by a simple forum search
Read
http://isp-control.net/forum/thread-1142...l#pid86386
---> if you want, maybe we can schedule an IRC session to talk about this.
Your action are not taken like provocations. For the trac issue, I've not removed your account. You should ask Malte for this issue. It's a strange story. You know, I have nothing against you. I would have preferred to continue working with you but unfortunately, you chose to leave the team. I resent you a bit for that.