search for: bivens

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

I have two servers each with one TDM card from Digium and three POTS lines going into each server (each POTS line is one individual number). and I want to have all incoming calls into server B be directed to the IVR on server A and to be able to fail over to Server B in case Server A has an issue (it can be a manual failover and I actually prefer it to be a manual process). I've

I upgraded an old Samba 2.x install on Debian that I had at a customer location. Authentication to the PDC was via winbind. Everything worked fine in the past except the RAID died so I rebuilt the RAID, copied over the old volume, and ran apt-get update && apt-get upgrade. Now I have some really weird Samba problems: I can connect to my share on Samba. I can create a dir, a file,

I upgraded an old Samba 2.x install on Debian that I had at a customer location. Authentication to the PDC was via winbind. Everything worked fine in the past except the RAID died so I rebuilt the RAID, copied over the old volume, and ran apt-get update && apt-get upgrade. Now I have some really weird Samba problems: I can connect to my share on Samba. I can create a dir, a file,

I have been asked to set up a customer with Exchange 2000. I have tried to convert them, so please don't suggest it. We have 3 boxes we can use to do this with. We want to use Samba 3 as the PDC (ldap backend) and Samba 3 as BDC (ldap backend), with the exchange box as a domain member. Will this work? If not, what is the best way to ensure that : a. We have PDC and BDC for authentication