| Bug #56010 | Spaces cause mysqld_safe not to start,my_print_defaults generated invalid output | ||
|---|---|---|---|
| Submitted: | 16 Aug 2010 12:20 | Modified: | 3 Sep 2010 15:04 |
| Reporter: | P Lekensteyn | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
| Version: | 5.1.49, 4.1, 5.0, 5.1, 5.6.99 | OS: | Linux (Debian Lenny) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution, my_print_defaults, mysqld_safe, spaces | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[16 Aug 2010 12:21]
P Lekensteyn
[17 Aug 2010 11:29]
P Lekensteyn
Patch for mysqld_safe, parse arguments line by line
Attachment: mysqld_safe.sh-print_defaults.patch (text/x-diff), 902 bytes.
[23 Aug 2010 13:08]
P Lekensteyn
Patch for mysqld_safe, parse_arguments line by line and import variables in local scope. The old patch wasn't working fully.
Attachment: mysqld_safe-print_defaults-rv2.patch (text/x-diff), 921 bytes.
