Bug #2758 --read-only option seems undocumented
Submitted: 12 Feb 2004 14:23 Modified: 20 Mar 2004 7:55
Reporter: Harrison Fisk Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0 OS:Any (All)
Assigned to: Guilhem Bichot CPU Architecture:Any
Triage: D4 (Minor)

[12 Feb 2004 14:23] Harrison Fisk
Description:
The --read-only option doesn't seem to appear at all in the manual, other than a changelog entry in MySQL 4.0.14.

How to repeat:
-- run the command
SHOW VARIABLES LIKE 'read_only';

-- Check out the show variables page or the SET page.
-- Notice that the variable isn't on there.

Suggested fix:
1.  Add the variable listed to the SHOW VARIABLES section.  Something similar to the change log should be fine:

read_only Available from 4.0.14. Causes mysqld to allow no updates except from slave threads or from users with the SUPER privilege. 

2.  Add it to the dynamic system variable section.

read_only  BOOL GLOBAL

3.  Possibly add a mention somewhere in replication since that is where it is useful.
[12 Feb 2004 14:35] Guilhem Bichot
I will do the SHOW VARIABLES part and when it's done I'll forward the rest to the docs team.
[20 Mar 2004 7:55] Guilhem Bichot
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

Now documented in all requested paragraphs.