Dyntex.net Support Centre: MySQL Reference Manual p.309

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 4: Database Administration 309 This contains information indicating when mysqld was started and stopped and also any critical errors found when running. If mysqld dies unexpectedly and safe_mysqld needs to restart mysqld, safe_mysqld will write a restarted mysqld row in this le. This log also holds a warning if mysqld notices a table that needs to be automatically checked or repaired. On some operating systems, the error log will contain a stack trace for where mysqld died. This can be used to nd out where mysqld died. See Section E.1.4 [Using stack trace], page 761. 4.9.2 The General Query Log If you want to know what happens within mysqld, you should start it with --log[=file]. This will log all connections and queries to the log le (by default named `'hostname'.log'). This log can be very useful when you suspect an error in a client and want to know exactly what mysqld thought the client sent to it. By default, the mysql.server script starts the MySQL server with the -l option. If you need better performance when you start using MySQL in a production environment, you can remove the -l option from mysql.server or change it to --log-bin. The entries in this log are written as mysqld receives the questions. This may be dierent from the order in which the statements are executed. This is in contrast to the update log and the binary log which are written after the query is executed, but before any locks are released. 4.9.3 The Update Log Note: the update log is replaced by the binary log. See Section 4.9.4 [Binary log], page 310. With this you can do anything that you can do with the update log. When started with the --log-update[=file_name] option, mysqld writes a log le con- taining all SQL commands that update data. If no lename is given, it defaults to the name of the host machine. If a lename is given, but it doesn't contain a path, the le is written in the data directory. If `file_name' doesn't have an extension, mysqld will create log le names like so: `file_name.###', where ### is a number that is incremented each time you execute mysqladmin refresh, execute mysqladmin flush-logs, execute the FLUSH LOGS statement, or restart the server. Note: for the above scheme to work, you must not create your own les with the same lename as the update log + some extensions that may be regarded as a number, in the directory used by the update log! If you use the --log or -l options, mysqld writes a general log with a lename of `hostname.log', and restarts and refreshes do not cause a new log le to be generated (although it is closed and reopened). In this case you can copy it (on Unix) by doing: mv hostname.log hostname-old.log mysqladmin flush-logs cp hostname-old.log to-backup-directory

MySQL Reference Manual

Our Partners

SpiritHost - web hosting for spiritual and education sites
SpiritHit.com - Religious and Spiritual Portal

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide