Requests to be added or dropped from the MySQL list should be
sent to the electronic mail address mdomo@tcx.se. Sending a
one-line message with body text of either subscribe mysql
or
unsubscribe mysql
will suffice. If your reply address is not
valid, you may use subscribe mysql your@address.your-domain
or
unsubscribe mysql your@address.your-domain
.
Please do not send mail about [un]subscribing to automatically forwarded to hundreds of other users.
Your local site may have many subscribers to mysql@tcx.se. In that
case, it may have a local mailing list, so that a single message from
tcx.se
is sent to the site and propagated to the local list. In
such cases, please contact your system administrator to be added to or
dropped from the local mysql@tcx.se list.
Mail to mdomo
is handled automatically by majordomo.
The following mailinglists exists:
mysql-announce
mysql
mysql-digest
mysql-Java
mysql-win32
myodbc
msql-mysql-modules
msql-mysql-modules-digest
You subscribe/unsubscribe to all lists in the same way as described
above. Just exchange mysql
with the list name.
Before you ask a question on the mailing list, it is a good idea to check this manual. If you can't find an answer here, check with your local MySQL expert. If you still can't find an answer to your question go ahead and read the next section about how to send mail to
If you can, please use the `mysqlbug' script that can be found in the scripts directory in the distribution. If that is not possible, remember to specify (if relevant) the following. Note that it is possible to answer a letter with too much information but not one with too little.
mysqladmin version
.
uname -a
.
If you are a support customer, please post the bug report to the specified mailing list for higher-priority treatment.
When answers are sent to you individually and not to the mailing list, it is considered good etiquette to summarise the answers and mail them to the mailing list.
Since it is very hard to now why something crashing please do one of the following things.
First try to check if thigs that work for other crash for you:
--with-debug
switch to
configure. This will include a safe memory allocator that can find some
errors. This also gives a lot of output about what is happening.
back
(or the backtrace command in your debugger) when
mysqld
core dumps.
Try to make your answer broad enough that people other than the original poster may benefit from it. If you consider your answer to have broad interest, you may want to post it to the mailing list instead of replying directly to the individual who asked. In such cases, please make sure that your answer is not a duplication of a previous answer.
Try to summarise the essential part of the question in your reply, but don't feel obliged to quote the whole question.
Go to the first, previous, next, last section, table of contents.