An error occurred fetching the project authors.
- 05 Oct, 2007 1 commit
-
-
unknown authored
Our web server has been restructured several times, and references to it in our source code has stayed the same. This patch from Paul DuBois updates all URLs to modern semantics. debian/po/ca.po: Change URLs. debian/po/cs.po: Change URLs. debian/po/da.po: Change URLs. debian/po/gl.po: Change URLs. debian/po/ja.po: Change URLs. debian/po/pt_BR.po: Change URLs. debian/po/sv.po: Change URLs. debian/po/tr.po: Change URLs. mysql-test/lib/mtr_report.pl: Change URLs. mysql-test/mysql-test-run-shell.sh: Change URLs. ndb/include/ndbapi/Ndb.hpp: Change URLs. netware/mysql_test_run.c: Change URLs. scripts/mysqld_safe.sh: Change URLs. sql/mysqld.cc: Change URLs.
-
- 24 Aug, 2007 1 commit
-
-
unknown authored
fixing bug#30624 scripts/mysqld_safe.sh: Fix last syslog -> want_syslog.
-
- 30 Jul, 2007 1 commit
-
-
unknown authored
Post-review fix, if 'logger' can't be found, and --syslog is requested, exit with error message instead of fall back to logging to error file. scripts/mysqld_safe.sh: Post-review fix, if 'logger' can't be found, and --syslog is requested, exit with error message instead of fall back to logging to error file.
-
- 27 Jul, 2007 1 commit
-
-
unknown authored
Don't use syslog by default; user will have to request it explicitly with the --syslog option. Use "sed -u" to get unbuffered output from sed, if it's supported. Otherwise, don't use sed at all - don't strip the timestamp from mysqld messages. Also, add new --syslog-tag=FOO option, which adds "-FOO" to the tag used when logging messages to syslog (i.e., mysqld-FOO or mysqld_safe-FOO) Also, explicitly mention where log messages are going, so user can more easily find them. Also, check if 'logger' is in the PATH, and log to the error log file if it can't be found.
-
- 09 Jul, 2007 2 commits
- 05 May, 2007 1 commit
-
-
unknown authored
mysqld_safe.sh: Overhaul the logging design, to allow logging mysqld messages to syslog. Add --syslog and --skip-syslog arguments for mysqld_safe. scripts/mysqld_safe.sh: Overhaul the logging design, to allow logging mysqld messages to syslog. Add two new options: --syslog and --skip-syslog. --syslog is the default, unless --log-error is also specified. If --log-error is specified (for mysqld_safe, mysqld, server, etc. - any group which mysqld_safe checks for arguments), then syslog is turned off. This is because mysqld will get the --log-error argument and log to a file anyways, which will be confusing to the user. If the user requests both --syslog and --log-error, a warning is printed (to mysqld_safe's stderr and to syslog), and we then behave as if --skip-syslog had been specified. Also, logging messages have been normalized somewhat: mysqld_safe now always prefixes messages with '<TIMESTAMP> mysqld_safe '. All messages go to the the console (stdout or stderr, depending on if it's a notice or an error) and to (the error log OR syslog). Also, a few cleanups while I'm here.
-
- 14 Dec, 2006 1 commit
-
-
unknown authored
-
- 10 May, 2006 1 commit
-
-
unknown authored
- Fix mysqld_safe so that it always passes correct --log-error argument to mysqld - A few other minor clean-ups to mysqld_safe scripts/mysqld_safe.sh: Bug #6061 mysql-log-rotate script - error logging doesn't use new file - Change mysqld_safe to pass --log-error to mysqld in all cases. The old behavior was to usually "swallow" the --log-error=file.name argument, which caused mysqld to write to stderr and not be able to flush the error log file. Ironically, passing --log-error (with no file name) seemed to work fine, because mysqld_safe didn't recognize it and passed it on to mysqld as an unknown option. - Ensure that the error log file matches what mysqld uses; in particular, add ".err" if given a --log-error argument with no extension, and add "$DATADIR" to the front of a relative path - Various other mysqld_safe clean-ups while there - quote arguments properly, remove some redundant code
-
- 18 Apr, 2006 1 commit
-
-
unknown authored
scripts/mysqld_safe.sh: Moved core file changing command outside of root-user only conditional
-
- 29 Mar, 2006 1 commit
-
-
unknown authored
Added --help option, bug#16392 acinclude.m4: Use "$shrext_cmds" when testing if shared library exists, bug#16332 acinclude.m4: Use "$shrext_cmds" when testing if shared library exists, bug#16332 scripts/mysqld_safe.sh: Added --help option, bug#16392
-
- 02 Mar, 2006 1 commit
-
-
unknown authored
Try find in order 'mysqld-nt', 'mysqld', 'mysqld-debug' and 'mysqld-max' mysqld_safe.sh: Don't try 'mysqld-max' before 'mysqld' if no server given, bug#17861 scripts/mysqld_safe.sh: Don't try 'mysqld-max' before 'mysqld' if no server given, bug#17861 mysql-test/mysql-test-run.pl: Try find in order 'mysqld-nt', 'mysqld', 'mysqld-debug' and 'mysqld-max'
-
- 31 Oct, 2005 1 commit
-
-
unknown authored
even when --ledir option is specified. (Bug #13774) scripts/mysqld_safe.sh: Figure out whether to use mysqld or mysqld-max after we have handled the command-line options and .cnf files.
-
- 25 Jun, 2005 1 commit
-
-
unknown authored
different DATADIR via the command line or during ./configure and still starting up mysqld_safe via a relative path. (Bug #7249) scripts/mysqld_safe.sh: Decouple figuring out which BASEDIR and DATADIR to use so that the only DATADIR we'll try to use without first verifying that it exists is the compiled-in default.
-
- 27 May, 2005 1 commit
-
-
unknown authored
Only add --defaults-extra-file=$DATADIR/my.cnf if $DATADIR/my.cnf is readable. scripts/mysqld_safe.sh: Only add --defaults-extra-file=$DATADIR/my.cnf if $DATADIR/my.cnf is readable. Without this patch, running mysqld_safe gives: Could not open required defaults file: /opt/home/tim/m/50/m/data/my.cnf Fatal error in defaults handling. Program aborted Could not open required defaults file: /opt/home/tim/m/50/m/data/my.cnf Fatal error in defaults handling. Program aborted These errors are printed by my_print_defaults; mysqld also encounters the same problem and quits.
-
- 20 Apr, 2005 1 commit
-
-
unknown authored
Rename 'IS_LINUX' configuration variable to 'TARGET_LINUX'.
-
- 02 Mar, 2005 1 commit
-
-
unknown authored
(Bug #8513) scripts/mysqld_safe.sh: Create directory for UNIX socket if it doesn't exist
-
- 23 Feb, 2005 1 commit
-
-
unknown authored
1) If my.cnf is found in datadir and basedir, give a warning and use the one in basedir. 2) If my.cnf is found in datadir, use it, but give a warning. 3) No warning if my.cnf is in basedir.
-
- 03 Feb, 2005 1 commit
-
-
unknown authored
scripts/mysqld_safe.sh: Add --help switch
-
- 05 Jan, 2005 1 commit
-
-
unknown authored
to only look for the mysqld binary (and english error strings) and assume the datadir from that. Then, if that datadir turns out to not exist, startup will fail. This avoids the behavior where mysqld_safe would go off and run a totally different binary because the data directory had been moved (even when --datadir was specified on the command line). (Bug #7249) scripts/mysqld_safe.sh: Don't actually verify that datadir exists when using relatively-located mysqld -- just assume that it does and either let it fail when it doesn't, or do the right thing when datadir is then set via the command line or my.cnf file.
-
- 04 Jan, 2005 2 commits
-
-
unknown authored
instead of DATADIR. include/config-win.h: Added checks for environment variable MYSQL_HOME libmysql/Makefile.shared: Added checks for environment variable MYSQL_HOME mysys/Makefile.am: Added checks for environment variable MYSQL_HOME mysys/default.c: Removed checks for my.cnf file in datadir, instead added checking if my.cnf exists in environment variable MYSQL_HOME scripts/mysqld_multi.sh: Added checks for my.cnf file in environment variable MYSQL_HOME, if exists. scripts/mysqld_safe.sh: Added checks for my.cnf file in environment variable MYSQL_HOME, if exists.
-
unknown authored
for port and/or pid-file parameters. (Bug #5878) scripts/mysqld_safe.sh: Change 'ps xa' to 'ps xaww' so whole command-line is examined
-
- 30 Nov, 2004 1 commit
-
-
unknown authored
Fix calls to my_print_defaults. Some how, --loose-verbose had been added before --no-defaults/defaults-file, which must be the first option. NOTE: this may make some installations behave differently, if they depend on this broken behavior. scripts/mysqld_safe.sh: Fix calls to my_print_defaults. Some how, --loose-verbose had been added before --no-defaults/defaults-file, which must be the first option. NOTE: this may make some installations behave differently, if they depend on this broken behavior.
-
- 03 Nov, 2004 1 commit
-
-
unknown authored
for Solaris test, and fix if @IS_LINUX@ test in mysqld_safe itself. configure.in: Portability fix for FIND_PROC setting; on Solaris (and probably others), 'ps -p $$' inside a shell script just returns 'sh' for command line, even though $0 contains the filename. So, use 'ps -fp $$' in the test (it shows the full command line, e.g., 'sh configure'). Leave the actual FIND_PROC command as-is, since mysqld itself is not a shell script. scripts/mysqld_safe.sh: Portability fix for mysqld_safe on non-Linux systems. A bogus use of 'if' and 'test' caused non-bash shells to enter a section meant to be run only on Linux systems. BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
- 07 Sep, 2004 1 commit
-
-
unknown authored
-
- 01 Sep, 2004 1 commit
-
-
unknown authored
bug #5001, added conditional if to test if port set, then only kill the processes for this port, not all processes (in the case of this bug where multiple servers are killed.) The change to the 'grep' to make sure mysqld_safe isn't killed was per Serg's discovery that mysqld_safe would get killed. In my testing, in killing one of the pids for a running server, the "if test ! -f $pid_file" was the case that evaluated as true, so in order to test, I had to comment that block out. scripts/mysqld_safe.sh: bug #5001, added conditional if to test if port set, then only kill the processes for this port, not all processes (in the case of this bug where multiple servers are killed.) The change to the 'grep' to make sure mysqld_safe isn't killed was per Serg's discovery that mysqld_safe would get killed. In my testing, in killing one of the pids for a running server, the "if test ! -f $pid_file" was the case that evaluated as true, so in order to test, I had to comment that block out.
-
- 10 Jun, 2004 1 commit
-
-
unknown authored
scripts/mysqld_safe.sh: don't protect mysqld from multiple --user commands - mysqld can take care of itself sql/mysqld.cc: warn about multiple --user parameters only if their arguments differ
-
- 28 Apr, 2004 1 commit
-
-
unknown authored
Output TIMESTAMP in 4.1 format for 4.1 tables (or for TIMESTAMP(19)) (portability fix) Fixed that INTERVAL can handle big integers. (Bug #3498) Fixed that hostname="" works identical as hostname="%" for table/column grants (Bug #3473) mysql-test/mysql-test-run.sh: Fixed wrong http address (Bug #3460) mysql-test/r/func_time.result: Results for new test cases mysql-test/t/func_time.test: Added test of INTERVAL with big integers scripts/mysqld_safe.sh: Added html address to manual in case of error sql/field.cc: Output TIMESTAMP in 4.1 format for 4.1 tables (or for TIMESTAMP(19)) sql/item_timefunc.cc: Fixed that INTERVAL can handle big integers. (Bug #3498) sql/mysql_priv.h: Removed not needed prototype sql/sql_acl.cc: Fixed that hostname="" works identical as hostname="%" for table/column grants (Bug #3473) Moved GRANT_TABLE::GRANT_TABLE functions ou from class definition to make it possible to debug them sql/structs.h: Fix for long values to INTERVAL
-
- 15 Jan, 2004 1 commit
-
-
unknown authored
started via mysqld_safe (BUG#2114) Thanks to Rodrigo Marchant for the suggestion scripts/mysqld_safe.sh: - fixed early removing of socket file when multiple instances of mysqld are started via the script (BUG#2114) Thanks to Rodrigo Marchant for the suggestion
-
- 19 Dec, 2003 1 commit
-
-
unknown authored
Bug #2163
-
- 27 Sep, 2003 1 commit
-
-
unknown authored
and [mysqld_safe] section in my.cnf, even if they are also specified in [mysql] section.
-
- 27 Aug, 2003 1 commit
-
-
unknown authored
and --defaults-file is a non-existing or non-regular file. Bug#755 scripts/mysqld_safe.sh: Added a warning to my_print_defaults if --verbose is given and --defaults-file is a non-existing or non-regular file. Bug#755
-
- 15 Jul, 2003 1 commit
-
-
unknown authored
in mysqld_safe (commented out by default), to not override any options defined in my.cnf (thanks to Axel Schwenke from Jobpilot.de for the suggestion)
-
- 14 Jun, 2003 1 commit
-
-
unknown authored
if one is running many mysqlds through mysqld_multi, for example. Without this option, on Linux one mysqld_safe process may kill other mysqlds as well, if started using the same binary and path.
-
- 12 Jun, 2003 1 commit
-
-
unknown authored
define a different niceness level in my.cnf (Bug #627) scripts/mysqld_safe.sh: - applied patch from Christian Hammers to be able to define a different niceness level in my.cnf (Bug #627)
-
- 15 Apr, 2003 1 commit
-
-
unknown authored
(bug #264)
-
- 16 Feb, 2003 1 commit
-
-
unknown authored
Reverted wrong patch for mysqld_safe.sh client/mysqldump.c: Patch for novell. scripts/mysqld_safe.sh: Reverted wrong patch. (We must delete the files first as otherwise we will get a problem if the files has the wrong permissions or if the machine went down without removing the socket file)
-
- 12 Feb, 2003 2 commits
- 28 Jan, 2003 1 commit
-
-
unknown authored
(On Windows --log-error is enabled by default) mysys/my_getopt.c: Call get_one_option() also for boolean values. scripts/mysqld_safe.sh: Add option --log-error sql/log.cc: Fix for --log-error sql/mysql_priv.h: Fix for --log-error sql/mysqld.cc: Fix for --log-error sql/sql_udf.cc: Lock the mysql/func table properly
-