From: jake%bugzilla.org <> Date: Sat, 18 Dec 2004 20:06:23 +0000 (+0000) Subject: Bug 247923 - The docs now specify the difference in syntax for MySQL 3/4 regarding... X-Git-Tag: bugzilla-2.16.8~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=700f9530fbf83bd95c0a9b4ef46842235e3a09da;p=thirdparty%2Fbugzilla.git Bug 247923 - The docs now specify the difference in syntax for MySQL 3/4 regarding the max_allowed_packet option. Patch by Shane H. W. Travis r=jake --- diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml index f1c433b2d2..5c6023bb19 100644 --- a/docs/xml/installation.xml +++ b/docs/xml/installation.xml @@ -242,47 +242,65 @@
MySQL - Visit the MySQL homepage at - www.mysql.com - to grab and install the latest stable release of the server. + + Visit the MySQL homepage at + www.mysql.com + to grab and install the latest stable release of MySQL. - Many of the binary - versions of MySQL store their data files in - /var. - On some Unix systems, this is part of a smaller root partition, - and may not have room for your bug database. You can set the data - directory as an option to configure - if you build MySQL from source yourself. + + Many of the binary versions of MySQL store their data files + in /var. On some Unix systems, this is + part of a smaller root partition, and may not have room for + your bug database. You can set the data directory as an + option to configure if you build MySQL + from source yourself. + - If you install from something other than an RPM or Debian - package, you will need to add mysqld - to your init scripts so the server daemon will come back up whenever - your machine reboots. Further discussion of UNIX init sequences are - beyond the scope of this guide. + + If you install from something other than an RPM or Debian + package, you will need to add mysqld + to your init scripts so the server daemon will come back up + whenever your machine reboots. Further discussion of UNIX + init sequences are beyond the scope of this guide. + + + + By default, MySQL will only accept packets up to 64Kb in size. + If you want to have attachments larger than this, you will need + to modify your /etc/my.cnf as below. + + + + If you are using MySQL 4.0 or newer, enter: + [mysqld] + # Allow packets up to 1M + max_allowed_packet=1M - Change your init script to start - mysqld - with the ability to accept large packets. By default, - mysqld - only accepts packets up to 64K long. This limits the size of - attachments you may put on bugs. If you add - - to the command that starts - mysqld - (or safe_mysqld), - then you will be able to have attachments up to about 1 megabyte. - There is a Bugzilla parameter for maximum attachment size; - you should configure it to match the value you choose here. - - If you plan on running Bugzilla and MySQL on the same machine, - consider using the - - option in the init script. This enhances security by preventing - network access to MySQL. + + If you are using an older version of MySQL, enter: + + [mysqld] + # Allow packets up to 1M + set-variable = max_allowed_packet=1M + + + There is also a parameter in Bugzilla called 'maxattachmentsize' + (default = 1000 Kb) that controls the maximum allowable attachment + size. Attachments larger than either the + 'max_allowed_packet' or 'maxattachmentsize' value will not be + accepted by Bugzilla. + + + + If you plan on running Bugzilla and MySQL on the same machine, + consider using the + option in the init script. This enhances security by preventing + network access to MySQL. +