erorr when patch --verbose -p1 /tmp/big-concurrency.patch
-- Patching file `qmail-send.c' using Plan A... Hunk #1 succeeded at 262. Hunk #2 FAILED at 908. Hunk #3 succeeded at 1547. Hunk #4 succeeded at 1555. 1 out of 4 hunks FAILED -- saving rejects to qmail-send.c.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |diff -u qmail-1.03.orig/spawn.c qmail-1.03/spawn.c |--- qmail-1.03.orig/spawn.c Mon Jun 15 03:53:16 1998 |+++ qmail-1.03/spawn.c Tue Jul 27 12:25:14 1999 -- Patching file `spawn.c' using Plan A... Hunk #1 succeeded at 63. Hunk #2 succeeded at 73. Hunk #3 succeeded at 156. Hunk #4 succeeded at 205. Hunk #5 FAILED at 241. 1 out of 5 hunks FAILED -- saving rejects to spawn.c.rej Hmm... Ignoring the trailing garbage. done Johan Almqvist wrote: * Felix von Leitner [EMAIL PROTECTED] [010329 19:43]: Thus spake Johan Almqvist ([EMAIL PROTECTED]): I wonder if anyone has written a real "bouncesaying" (qmails bouncesaying just exits with an exit code that makes qmail-local do the actual bouncing. And what is your problem with that? I can't manually bounce a message from, say, mutt. -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/ Part 1.2Type: application/pgp-signature
Re: big-concurrency.patch
Martin: Ok! .. thanks! U.. It's posible when I apply this change the performance of the machine turn slowly? Martin Volesky wrote: On 09/12/00 at 3:21 PM Federico Edelman Anaya wrote: A few days ago .. I post on the list many question about big-concurrency.patch ... I was reading other list about Qmail and I get this solution about the problem with the FD .. The solution was: echo "65536" /proc/sys/fs/inode-max echo "16384" /proc/sys/fs/file-max So.. you need to do this every system reboot, I don't know how to make this persistent.. anybody have idea or know how to make this persistent? Under Liux 2.2.x, the way to make this persistent is to use the sysctl facility. add: fs.file-max = 16384 fs.inode-max = 65536 to the sysctl.conf file in /etc, and it will be loaded up evey time you boot the machine. Martin Volesky - [EMAIL PROTECTED] CTO - Deijlabs Corporation 1221 Mackay, Suite 200 Montreal, Quebec, Canada H3G 2H5 Tel.: 514.399.9930 Fax.: 514.399.1117
Re: big-concurrency.patch
On 11/12/00 at 12:30 PM Federico Edelman Anaya wrote: Martin: Ok! .. thanks! U.. It's posible when I apply this change the performance of the machine turn slowly? Federico, There is no reason why your system should run any slower because of the sysctl.conf modifications. Martin Volesky wrote: Under Liux 2.2.x, the way to make this persistent is to use the sysctl facility. add: fs.file-max = 16384 fs.inode-max = 65536 to the sysctl.conf file in /etc, and it will be loaded up evey time you boot the machine. Martin Volesky - [EMAIL PROTECTED] CTO - Deijlabs Corporation 1221 Mackay, Suite 200 Montreal, Quebec, Canada H3G 2H5 Tel.: 514.399.9930 Fax.: 514.399.1117
Re: big-concurrency.patch
Martin Volesky [EMAIL PROTECTED] wrote: On 11/12/00 at 12:30 PM Federico Edelman Anaya wrote: U.. It's posible when I apply this change the performance of the machine turn slowly? There is no reason why your system should run any slower because of the sysctl.conf modifications. At least as compared to having made the changes manually after boot. However, his system could exhibit poorer interactive response compared to before modifying the max-files and max-inodes due to the increased load from qmail. 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 11/12/00 at 2:25 PM Charles Cazabon wrote: At least as compared to having made the changes manually after boot. However, his system could exhibit poorer interactive response compared to before modifying the max-files and max-inodes due to the increased load from qmail. Charles Yes Charles, I agree with all your points. Martin Volesky - [EMAIL PROTECTED] CTO - Deijlabs Corporation 1221 Mackay, Suite 200 Montreal, Quebec, Canada H3G 2H5 Tel.: 514.399.9930 Fax.: 514.399.1117
Re: big-concurrency.patch
On 09/12/00 at 3:21 PM Federico Edelman Anaya wrote: A few days ago .. I post on the list many question about big-concurrency.patch ... I was reading other list about Qmail and I get this solution about the problem with the FD .. The solution was: echo "65536" /proc/sys/fs/inode-max echo "16384" /proc/sys/fs/file-max So.. you need to do this every system reboot, I don't know how to make this persistent.. anybody have idea or know how to make this persistent? Under Liux 2.2.x, the way to make this persistent is to use the sysctl facility. add: fs.file-max = 16384 fs.inode-max = 65536 to the sysctl.conf file in /etc, and it will be loaded up evey time you boot the machine. Martin Volesky - [EMAIL PROTECTED] CTO - Deijlabs Corporation 1221 Mackay, Suite 200 Montreal, Quebec, Canada H3G 2H5 Tel.: 514.399.9930 Fax.: 514.399.1117
big-concurrency.patch
A few days ago .. I post on the list many question about big-concurrency.patch ... I was reading other list about Qmail and I get this solution about the problem with the FD .. This is the log whit error: Report of Qmailanalog: - Errors of FD?: 24 6.36 /bin/sh: /usr/bin/ezmlm-return: Too many open files in system/ 16 28.13 /bin/sh: /usr/bin/ezmlm-weed: Too many open files in system/ 92 27.81 /bin/sh: error in loading shared libraries: libc.so.6: cannot open shared object file: Error 23/ 59 41.43 /bin/sh: error in loading shared libraries: libdl.so.2: cannot open shared object file: Error 23/ 48 63.30 /bin/sh: error in loading shared libraries: libncurses.so.5: cannot open shared object file: Error 23/ 58 18.57 /usr/bin/ezmlm-return: error in loading shared libraries: libc.so.6: cannot open shared object file: Error 23/ 106 37.99 /usr/bin/ezmlm-return: error in loading shared libraries: libcrypt.so.1: cannot open shared object file: Error 23/ 4 1.46 /usr/bin/ezmlm-return: error in loading shared libraries: libm.so.6: cannot open shared object file: Error 23/ - Other error: 851 3182.23 Connected to 200.41.50.10 but connection died. (#4.4.2)/ 1 60.03 Connected to 200.41.50.7 but connection died. (#4.4.2)/ 316 12453.57 Connected to 200.41.50.9 but connection died. (#4.4.2)/ 1 0.20 Sorry, I couldn't find any host by that name. (#4.1.2)/ 30.74 bin/qmail-local: error in loading shared libraries: libc.so.6: cannot open shared object file: Error 23/ The solution was: echo "65536" /proc/sys/fs/inode-max echo "16384" /proc/sys/fs/file-max So.. you need to do this every system reboot, I don't know how to make this persistent.. anybody have idea or know how to make this persistent? Thanks :)
Re: big-concurrency.patch
Federico Edelman Anaya [EMAIL PROTECTED] wrote: The solution was: echo "65536" /proc/sys/fs/inode-max echo "16384" /proc/sys/fs/file-max So.. you need to do this every system reboot, I don't know how to make this persistent.. anybody have idea or know how to make this persistent? This is really more of a Unix/Linux question than anything else. However, try adding those two lines to the end of /etc/rc.d/rc.local or your system's equivalent. 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 Sat, Dec 09, 2000 at 12:31:16PM -0600, Charles Cazabon wrote: echo "65536" /proc/sys/fs/inode-max echo "16384" /proc/sys/fs/file-max This is really more of a Unix/Linux question than anything else. However, try adding those two lines to the end of /etc/rc.d/rc.local or your system's equivalent. Also, realize that by default user's are limited to 1024 open files unless you use ulimit -n to increase it. Sean -- It's bad precident for a president to win through illegal influence of the ballots and election process. Sean Reifschneider, Inimitably Superfluous [EMAIL PROTECTED] tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
Installing big-concurrency.patch
Hi, What's the correct procedure for installing the big-concurrency patch on a live system? Is it just a patch, make, make setup check, restart qmail? Or will it affect/break anything else? Thanks, Brian -- Brian Baquiran [EMAIL PROTECTED] http://www.baquiran.com/ AIM: bbaquiran Work: (632)718 Home: (632)9227123
Re: Installing big-concurrency.patch
[EMAIL PROTECTED] wrote: What's the correct procedure for installing the big-concurrency patch on a live system? Is it just a patch, make, make setup check, restart qmail? Or will it affect/break anything else? This advice applies ONLY to the big-concurrency patch (specifically, the one from www.qmail.org). Other big-* patches are not quite as forgiving. I would stop qmail before doing make setup (or moving qmail-send and qmail-?spawn into place). qmail-send runs as a daemon that starts qmail-?spawn, if the running version of qmail-send doesn't speak the same language as the invokable versions of qmail-?spawn, you could run into some trouble. If you're doing a live heavy-duty mission-critical production server, test out the patch (and your planned patch procedure) on another server first. Mark -- Do not reply directly to this e-mail address -- Mark Mentovai UNIX Engineer Gillette Global Network
Re: Installing big-concurrency.patch
2000-06-27, at 02:00:20, [EMAIL PROTECTED] wrote: Hi, What's the correct procedure for installing the big-concurrency patch on a live system? Is it just a patch, make, make setup check, restart qmail? Or will it affect/break anything else? I donna know what's in your case but I would first back up /var/qmail structure (without queue of course) and then trying to put any patches... i.e. at night : -- cheers, Sylwester S. Biernacki [EMAIL PROTECTED]
