search for: 22997

...472 S 0.7 0.0 0:03.68 atack 23479 apache 15 0 964 556 472 S 0.7 0.0 0:01.94 atack 22170 apache 15 0 964 560 472 S 0.3 0.0 0:05.23 atack 22375 apache 15 0 964 560 472 S 0.3 0.0 0:04.21 atack 22858 apache 15 0 964 560 472 S 0.3 0.0 0:02.87 atack 22997 apache 15 0 964 560 472 S 0.3 0.0 0:04.11 atack 22999 apache 15 0 964 560 472 S 0.3 0.0 0:02.22 atack 23007 apache 15 0 964 560 472 S 0.3 0.0 0:03.79 atack 23099 apache 15 0 964 556 472 S 0.3 0.0 0:02.18 atack 23101 apache 15 0 964 556 47...

I''ve got something that I''m not sure is actually doable. I have a very complex model relationship with a lot of parent/child/grandchild/ greatgrandchild etc stuff going on. Is there a way to do a route like this? tld.com/ projects/:project_name/:sequence_acronym/:shot_number/:department/:eleme nt_name/:version/ where: project is the parent of sequence sequence is the

...CE[22998]: chan_iax2.c:8775 update_registry: Restricting registration for peer 'modem2' to 60 seconds (requested 300) [Jul 4 17:44:08] NOTICE[22992]: chan_iax2.c:8775 update_registry: Restricting registration for peer 'modem99' to 60 seconds (requested 300) [Jul 4 17:44:09] NOTICE[22997]: chan_iax2.c:8775 update_registry: Restricting registration for peer 'modem3' to 60 seconds (requested 300) [Jul 4 17:44:11] NOTICE[22994]: chan_iax2.c:8775 update_registry: Restricting registration for peer 'modem5' to 60 seconds (requested 300) [Jul 4 17:44:16] NOTICE[22998]: c...

Hi, In our company we are currently running a Samba server and Windows XP clients. At the moment we are having problems with mapping Samba shares in Windows. Shares are being mapped through a windows startup script, which executes net use (with the option persistent:no) command. For most users this works most of the time, nevertheless it often fails, the exect reason for this isn't clear

Hi, I have mongrel 0.3.14, with ruby 1.8.5, rails 1.1.6 and mongrel cluster 0.2.1, on debian sage 3.1 with apache 2.0, and fastthread 0.6.1. I am load balancing 3 mongrel processes using the random port trick. When I start mongrel the processes have about 60MB, but after some hour of usage the memory ballons upto more than 180MB and the site becomes terribly slow. Forcing me to restart mongrel