Here's how I know: Oops. Your system's FD_SET() has a hidden limit of 1024 descriptors. This means that the qmail daemons could crash if you set the run-time concurrency higher than 509. So I'm going to insist that the concurrency limit in conf-spawn be at most 509. Right now it's 2048. I tried modifying the code so it would let it compile with my value, but it crashed qmail once I hit 510 for concurrency. This is a well known issue on the qmail mailing list. With kernel 2.2, it was possible to find a canned patch for the kernel, apply it, recompile, and you were good. However, with kernel 2.4, I can't find a patch. Also, apparently the patch does not play nice with certain scsi drivers, and since you have to recompile everything, including modules, I'm SOL since my main servers that I run it on have a raid card for which the driver source is not available (thanks Dell). Jay > -----Original Message----- > From: Scott Dier [mailto:dieman+tclug at ringworld.org] > Sent: Thursday, November 01, 2001 5:24 PM > To: tclug-list at mn-linux.org > Subject: [TCLUG] Re: Freebsd lovin' > > > * Austad, Jay <austad at marketwatch.com> [011101 16:30]: > > Primarily, I did it for a qmail server. With linux, I was > limited to > > 509 concurrent outgoing connections without patching the > kernel, and > > no patch > > How are you making this conclusion? > > -- > Scott Dier <dieman at ringworld.org> <sdier at debian.org> http://www.ringworld.org/ #linuxos at irc.openprojects.net Just say NO to Product Activation! _______________________________________________ Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.mn-linux.org/mailman/listinfo/tclug-list