Re: big-concurrency patch
On Mon, Jun 04, 2001 at 05:14:00PM -0400, Mark Douglas wrote: > No, I can make this patch cleanly on a linux based system no problem, but > when I try the same approach on the solaris system, it doesn't work. You may need GNU patch, binary called gpatch on BSD systems if installed. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: big-concurrency patch
Title: RE: big-concurrency patch Sorry, maybe you are in the wrong directory? you should not be in the qmail-1.03 dir. because the patch specifies the path already "qmail-1.03/file-to-patch". so if you are in the qmail dir , do a "cd .." and try the patch again. if it still can't work then follow my first instruction, get another version of the tool "patch". Hope this helps Paul - Original Message - From: Mark Douglas To: '[EMAIL PROTECTED]' Sent: Tuesday, June 05, 2001 3:36 AM Subject: RE: big-concurrency patch I've tried all kinds of -p options, and left it out, and it doesn't help. Also, as for it not being the standard big-concurrency patch, would you tell me which one is? Even the one right on qmail's home site is that same patch muddled in with the e-mail. Thanks, Mark -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 15:04 To: '[EMAIL PROTECTED]' Subject: Re: big-concurrency patch Mark Douglas <[EMAIL PROTECTED]> wrote: > I'm having problems applying this patch. I can't find any documentation for > it, and the patch file itself seems to be rather chopped up. I did my best > to put it into appropriate patch files, but when I run patch -p1 < > big-concurrency.patch it asks me what file I want to patch. That's a clue that you're using the wrong argument to the -p option. However, it could have another cause -- the patch you pointed to isn't the standard big-concurrency one; the message above the patch states: This is the patch that I use at suse.com. We do almost 1 million messages a day with this patch and concurrencyremote set to 400. This patch comes with the standard disclaimer. No warranty, it may not work, etc. But it works for me :) It's also not pretty. It's against qmail-1.03+verh-0.02 (the ezmlm patch l and h patch). So the offsets may be off a little bit. So it's not against standard qmail; it's against qmail 1.03 after the verh patch has been applied. If you're not using that patch as well, it's not surprising it won't apply cleanly. Try against a vanilla qmail 1.03 source tree. Charles -- --- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: big-concurrency patch
Title: RE: big-concurrency patch What operating system are you compiling on? maybe you want to try another version of patch from ftp.gnu.org . Because the same thing happened to me when i compiled on solaris 8 and using another version of patch helped. Hope it works for you Paul - Original Message - From: Mark Douglas To: '[EMAIL PROTECTED]' Sent: Tuesday, June 05, 2001 3:36 AM Subject: RE: big-concurrency patch I've tried all kinds of -p options, and left it out, and it doesn't help. Also, as for it not being the standard big-concurrency patch, would you tell me which one is? Even the one right on qmail's home site is that same patch muddled in with the e-mail. Thanks, Mark -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 15:04 To: '[EMAIL PROTECTED]' Subject: Re: big-concurrency patch Mark Douglas <[EMAIL PROTECTED]> wrote: > I'm having problems applying this patch. I can't find any documentation for > it, and the patch file itself seems to be rather chopped up. I did my best > to put it into appropriate patch files, but when I run patch -p1 < > big-concurrency.patch it asks me what file I want to patch. That's a clue that you're using the wrong argument to the -p option. However, it could have another cause -- the patch you pointed to isn't the standard big-concurrency one; the message above the patch states: This is the patch that I use at suse.com. We do almost 1 million messages a day with this patch and concurrencyremote set to 400. This patch comes with the standard disclaimer. No warranty, it may not work, etc. But it works for me :) It's also not pretty. It's against qmail-1.03+verh-0.02 (the ezmlm patch l and h patch). So the offsets may be off a little bit. So it's not against standard qmail; it's against qmail 1.03 after the verh patch has been applied. If you're not using that patch as well, it's not surprising it won't apply cleanly. Try against a vanilla qmail 1.03 source tree. Charles -- --- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: big-concurrency patch
On Mon, Jun 04, 2001 at 04:25:58PM -0600, Charles Cazabon wrote: > Mark Douglas <[EMAIL PROTECTED]> wrote: > > No, I can make this patch cleanly on a linux based system no problem, but > > when I try the same approach on the solaris system, it doesn't work. Was the > > test you're doing from a solaris system? > > Nope, Linux. Perhaps the version of patch which Sun ships is broken? Most of > the rest of their tools seem to be :). You are correct. Get the latest version of GNU patch from ftp://ftp.gnu.org/gnu/patch and install it on your server. Personally, I like to keep my namespaces separate for GNU tools on Solaris, so that I always know which version of a program I'm running. You can do this for most GNU utils with the following configuration parameter: # ./configure --program-prefix=g --Adam
Re: big-concurrency patch
Mark Douglas <[EMAIL PROTECTED]> wrote: > No, I can make this patch cleanly on a linux based system no problem, but > when I try the same approach on the solaris system, it doesn't work. Was the > test you're doing from a solaris system? Nope, Linux. Perhaps the version of patch which Sun ships is broken? Most of the rest of their tools seem to be :). Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: big-concurrency patch
On Mon, Jun 04, 2001 at 05:14:00PM -0400, Mark Douglas allegedly wrote: > No, I can make this patch cleanly on a linux based system no problem, but > when I try the same approach on the solaris system, it doesn't work. Was the > test you're doing from a solaris system? At this point I'm just kind of > wondering what the problem is with the solaris system, because I took the > patched version from the linux box and moved it to the solaris one and > recompiled without any problems. Solaris has it's own patch program. Try installing and using the "real" one. Regards.
RE: big-concurrency patch
Title: RE: big-concurrency patch No, I can make this patch cleanly on a linux based system no problem, but when I try the same approach on the solaris system, it doesn't work. Was the test you're doing from a solaris system? At this point I'm just kind of wondering what the problem is with the solaris system, because I took the patched version from the linux box and moved it to the solaris one and recompiled without any problems. Thanks, Mark -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 16:27 To: '[EMAIL PROTECTED]' Subject: Re: big-concurrency patch Mark Douglas <[EMAIL PROTECTED]> wrote: > I've tried all kinds of -p options, and left it out, and it doesn't help. > > Also, as for it not being the standard big-concurrency patch, would you tell > me which one is? Even the one right on qmail's home site is that same patch > muddled in with the e-mail. I tried it here, and it applies cleanly: [charlesc@charon qmail-test]$ wget http://www.qmail.org/big-concurrency.patch --14:19:19-- http://www.qmail.org:80/big-concurrency.patch => `big-concurrency.patch' Connecting to www.qmail.org:80... connected! HTTP request sent, awaiting response... 200 OK Length: 9,331 [text/plain] 0K -> . [100%] 14:19:24 (9.19 KB/s) - `big-concurrency.patch' saved [9331/9331] [charlesc@charon qmail-test]$ ls -l -rw-r--r-- 1 charlesc qcc 9331 Aug 12 1999 big-concurrency.patch [charlesc@charon qmail-test]$ tar xzf qmail-1.03.tar.gz [charlesc@charon qmail-test]$ cd qmail-1.03 [charlesc@charon qmail-1.03]$ cat ../big-concurrency.patch | patch -p1 patching file `chkspawn.c' patching file `conf-spawn' patching file `qmail-send.c' patching file `spawn.c' [charlesc@charon qmail-1.03]$ You must be using patch incorrectly. For this patch, you should be in the unpacked qmail source tree top directory, and strip one directory component (-p1). Perhaps you were in the wrong directory? Charles -- --- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
RE: big-concurrency patch
> to put it into appropriate patch files, but when I run patch -p1 < > big-concurrency.patch it asks me what file I want to patch. Strictly speaking, it's /possible/ that your version of patch is getting screwed up by the email header. Try removing everything above the first 'diff' line. Then copy it to your qmail-1.03 src directory, then just try counting your peas. :) patch -p0
Re: big-concurrency patch
Mark Douglas <[EMAIL PROTECTED]> wrote: > I've tried all kinds of -p options, and left it out, and it doesn't help. > > Also, as for it not being the standard big-concurrency patch, would you tell > me which one is? Even the one right on qmail's home site is that same patch > muddled in with the e-mail. I tried it here, and it applies cleanly: [charlesc@charon qmail-test]$ wget http://www.qmail.org/big-concurrency.patch --14:19:19-- http://www.qmail.org:80/big-concurrency.patch => `big-concurrency.patch' Connecting to www.qmail.org:80... connected! HTTP request sent, awaiting response... 200 OK Length: 9,331 [text/plain] 0K -> . [100%] 14:19:24 (9.19 KB/s) - `big-concurrency.patch' saved [9331/9331] [charlesc@charon qmail-test]$ ls -l -rw-r--r-- 1 charlesc qcc 9331 Aug 12 1999 big-concurrency.patch [charlesc@charon qmail-test]$ tar xzf qmail-1.03.tar.gz [charlesc@charon qmail-test]$ cd qmail-1.03 [charlesc@charon qmail-1.03]$ cat ../big-concurrency.patch | patch -p1 patching file `chkspawn.c' patching file `conf-spawn' patching file `qmail-send.c' patching file `spawn.c' [charlesc@charon qmail-1.03]$ You must be using patch incorrectly. For this patch, you should be in the unpacked qmail source tree top directory, and strip one directory component (-p1). Perhaps you were in the wrong directory? Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
RE: big-concurrency patch
Title: RE: big-concurrency patch I've tried all kinds of -p options, and left it out, and it doesn't help. Also, as for it not being the standard big-concurrency patch, would you tell me which one is? Even the one right on qmail's home site is that same patch muddled in with the e-mail. Thanks, Mark -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Monday, June 04, 2001 15:04 To: '[EMAIL PROTECTED]' Subject: Re: big-concurrency patch Mark Douglas <[EMAIL PROTECTED]> wrote: > I'm having problems applying this patch. I can't find any documentation for > it, and the patch file itself seems to be rather chopped up. I did my best > to put it into appropriate patch files, but when I run patch -p1 < > big-concurrency.patch it asks me what file I want to patch. That's a clue that you're using the wrong argument to the -p option. However, it could have another cause -- the patch you pointed to isn't the standard big-concurrency one; the message above the patch states: This is the patch that I use at suse.com. We do almost 1 million messages a day with this patch and concurrencyremote set to 400. This patch comes with the standard disclaimer. No warranty, it may not work, etc. But it works for me :) It's also not pretty. It's against qmail-1.03+verh-0.02 (the ezmlm patch l and h patch). So the offsets may be off a little bit. So it's not against standard qmail; it's against qmail 1.03 after the verh patch has been applied. If you're not using that patch as well, it's not surprising it won't apply cleanly. Try against a vanilla qmail 1.03 source tree. Charles -- --- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: big-concurrency patch
Mark Douglas <[EMAIL PROTECTED]> wrote: > I'm having problems applying this patch. I can't find any documentation for > it, and the patch file itself seems to be rather chopped up. I did my best > to put it into appropriate patch files, but when I run patch -p1 < > big-concurrency.patch it asks me what file I want to patch. That's a clue that you're using the wrong argument to the -p option. However, it could have another cause -- the patch you pointed to isn't the standard big-concurrency one; the message above the patch states: This is the patch that I use at suse.com. We do almost 1 million messages a day with this patch and concurrencyremote set to 400. This patch comes with the standard disclaimer. No warranty, it may not work, etc. But it works for me :) It's also not pretty. It's against qmail-1.03+verh-0.02 (the ezmlm patch l and h patch). So the offsets may be off a little bit. So it's not against standard qmail; it's against qmail 1.03 after the verh patch has been applied. If you're not using that patch as well, it's not surprising it won't apply cleanly. Try against a vanilla qmail 1.03 source tree. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
big-concurrency patch
Title: big-concurrency patch I'm having problems applying this patch. I can't find any documentation for it, and the patch file itself seems to be rather chopped up. I did my best to put it into appropriate patch files, but when I run patch -p1 < big-concurrency.patch it asks me what file I want to patch. I'm not a programmer, and have no idea what files need to be patched. I don't want to screw anything up (although I have made a backup of my current source directory). Can anybody point me in the right direction? This is the big-concurrency.patch I'm using: http://www.glasswings.com.au/qmail/big-concurrency.patch Mark Douglas - Architecture Sympatico-Lycos Inc. All your base are belong to us! Make your time!
Re: multiple qmail installations vs. big concurrency patch
On Thu, Apr 19, 2001 at 05:31:52PM -0700, Brett wrote: > Setting up /var/qmail1, /var/qmail2, etc. each with a concurrency of, say, > 100, as opposed to one install of qmail with the big concurrency remote > patch with concurrency set to 500. This might, IMHO, have some advantages, especially if /var/qmail1 and /var/qmail2 are different spindles. However, see below. > > Apparently you have to adjust the linux kernel to get your concurrency up to > 500 so wouldn't it be easier to just have multiple qmail installs? Is there > an overall limit of concurrent connections that's unrelated to whether > you're running one or several qmail installs? Thanks. Yes, the kernel is the limit -- maximum running processes, maximum open file descriptors, etc. The kernel limits that you'd likely run into would be the system-wide ones, not just per-process ones. I don't believe that kernel recompiles are required anymore, though -- check /proc/sys/fs/file-max and /proc/sys/fs/inode-max tunables, and 'man bash' for ulimit options -- kernel options for open file descriptors do not seem to be hard-coded anymore (since 2.2.12 IIRC). > > -- Greg White Those who make peaceful revolution impossible will make violent revolution inevitable. -- John F. Kennedy
multiple qmail installations vs. big concurrency patch
Setting up /var/qmail1, /var/qmail2, etc. each with a concurrency of, say, 100, as opposed to one install of qmail with the big concurrency remote patch with concurrency set to 500. Apparently you have to adjust the linux kernel to get your concurrency up to 500 so wouldn't it be easier to just have multiple qmail installs? Is there an overall limit of concurrent connections that's unrelated to whether you're running one or several qmail installs? Thanks.
RE: How to add big-todo and big-concurrency patch ?
On Sun, 11 Mar 2001 [EMAIL PROTECTED] wrote: > How can I check whether the patch was successfully installed or not ? Patch will exit with no errors. -- Todd A. Jacobs CodeGnome Consulting, LTD
RE: How to add big-todo and big-concurrency patch ?
How can I check whether the patch was successfully installed or not ? Rgds Ronnie * qmail newbie * -Original Message- From: Todd A. Jacobs [mailto:[EMAIL PROTECTED]] Sent: Friday, March 09, 2001 5:38 PM To: Thum Chee Weng, Ronnie Cc: [EMAIL PROTECTED] Subject: RE: How to add big-todo and big-concurrency patch ? On Fri, 9 Mar 2001 [EMAIL PROTECTED] wrote: > It's a text file, rite. But the 1st few lines looks like a readme. why > ? Can i just save the file as 'big-todo.103.patch' in my qmail server > and run the patch. Yes. Patch is pretty smart about that sort of thing. :) -- Todd A. Jacobs CodeGnome Consulting, LTD This email had been checked by Asiatravelmart.com's Virus Scanner. Please email any questions to [EMAIL PROTECTED]
RE: How to add big-todo and big-concurrency patch ?
On Fri, 9 Mar 2001 [EMAIL PROTECTED] wrote: > It's a text file, rite. But the 1st few lines looks like a readme. why > ? Can i just save the file as 'big-todo.103.patch' in my qmail server > and run the patch. Yes. Patch is pretty smart about that sort of thing. :) -- Todd A. Jacobs CodeGnome Consulting, LTD
RE: How to add big-todo and big-concurrency patch ?
It's a text file, rite. But the 1st few lines looks like a readme. why ? Can i just save the file as 'big-todo.103.patch' in my qmail server and run the patch. Rgds Ronnie -Original Message- From: Todd A. Jacobs [mailto:[EMAIL PROTECTED]] Sent: Friday, March 09, 2001 3:07 PM To: Thum Chee Weng, Ronnie Cc: [EMAIL PROTECTED] Subject: Re: How to add big-todo and big-concurrency patch ? On Fri, 9 Mar 2001 [EMAIL PROTECTED] wrote: > 1. Where to get it ? http://qmail.valueclick.com/qmail/big-todo.103.patch > 2. How to install it ? Halt qmail. Run patch on the patchfile (probably 'patch -p0 < big-todo.103.patch' from within your qmail-1.03 source directory) and then 'make && make setup check' to recompile. -- Todd A. Jacobs CodeGnome Consulting, LTD This email had been checked by Asiatravelmart.com's Virus Scanner. Please email any questions to [EMAIL PROTECTED]
Re: How to add big-todo and big-concurrency patch ?
On Fri, 9 Mar 2001 [EMAIL PROTECTED] wrote: > 1. Where to get it ? http://qmail.valueclick.com/qmail/big-todo.103.patch > 2. How to install it ? Halt qmail. Run patch on the patchfile (probably 'patch -p0 < big-todo.103.patch' from within your qmail-1.03 source directory) and then 'make && make setup check' to recompile. -- Todd A. Jacobs CodeGnome Consulting, LTD
How to add big-todo and big-concurrency patch ?
Hi, I've come across the above patch that is suppose make qmail able to handle more outgoing emails than the default setting. 1. Where to get it ? 2. How to install it ? Rgds Ronnie (ext 3210) MCP, MCP+I, MCSE This email had been checked by Asiatravelmart.com's Virus Scanner. Please email any questions to [EMAIL PROTECTED]
