View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000530 | MySQL v5 for OS/2 & eComStation | Bug | public | 2012-03-20 02:41 | 2022-05-14 06:43 |
| Reporter | LewisR | Assigned To | psmedley | ||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0000530: MySQL 5.1.61 default config file fails with socket directive | ||||
| Description | my-medium.cnf contains the following socket references: # The following options will be passed to all MySQL clients [client] socket = \socket\MySQL # Here follows entries for some specific programs # The MySQL server [mysqld] socket = \socket\MySQL When the server comes up, it complains about not being able to locate "ocket\MySQL". Likewise, when starting mysqladmin, a similar message is displayed. | ||||
| Steps To Reproduce | 1. Copy my-medium.cnf to %ETC%\my.cnf (do not edit). 2. Start mysqld.exe. 3. Error displays (along with a warning about skip-locking becoming deprecated, and to use skip-external-locking). 4. Daemon shuts down. | ||||
| Additional Information | The first line in the daemon window is the old "TlsAllocThreadLocalMemory error: init already done!" error, which is apparently cosmetic. The default cnf should be changed to update the skip-locking directive to skip-external-locking (I've used this syntax on NetWare since 5.0; I'm not sure why the default config files do not include it). However, commenting the socket directives results in the server and the client(s) utilizing the default socket (\socket\MySQL) without complaint. It is only when explicitly stated in my.cnf that this is an issue. The server in question is a fresh (last week) install of eCS 2.1 running the latest available GCC 4 core and libc064.dll (full libc063.dll, *not* the forwarder). The hardware is an HP Proliant ML370 G2 with 4GB RAM. | ||||
| Tags | No tags attached. | ||||
|
|
can you try \\socket\\MySQL |
|
|
Confirmed, Paul. Escaping the backslashes does the trick. I didn't try it, but would it then be reasonable to expect that the second backslash is safe, i.e.: \\socket\MySQL ? I should have thought to try your suggestion before posting. ;-) Thanks. |
|
|
Hi Lewis, Glad it helped. I would have thought \\socket\mysql wouldn't work either - but your error suggests it might... |
|
|
Indeed, Paul. I just tested again. \\socket\MySQL works just as well. ;-) So, however, you want to close this ticket is fine by me. You could add this as a readme item or if your packaging system allows you to tweak the sample config files, either should do. It's just another one of those little "head scratchers" when first configuring, that's all. Cheers/2 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-03-20 02:41 | LewisR | New Issue | |
| 2012-03-25 02:11 | psmedley | Note Added: 0002227 | |
| 2012-03-25 04:06 | LewisR | Note Added: 0002228 | |
| 2012-03-25 04:35 | psmedley | Note Added: 0002229 | |
| 2012-03-25 05:17 | LewisR | Note Added: 0002230 | |
| 2022-05-14 06:43 | psmedley | Assigned To | => psmedley |
| 2022-05-14 06:43 | psmedley | Status | new => resolved |
| 2022-05-14 06:43 | psmedley | Resolution | open => no change required |
