Commit 93e1030d authored by unknown's avatar unknown
Browse files

Bug #22860: Option --memlock should be revisited 

Support says that memlock doesn't work on OSes other than Solaris.  
Add a warning about --memlock to the crash monologue.


sql/mysqld.cc:
  On a crash when --memlock was active, emit advice about the insta-
  bility of that parameter.
parent 02e764bd

BitKeeper/etc/collapsed

+2 −0
Original line number Diff line number Diff line 
452a92d0-31-8wSzSfZi165fcGcXPA

454a7ef8gdvE_ddMlJyghvOAkKPNOQ

454f8960jsVT_kMKJtZ9OCgXoba0xQ

4554a95d7txO1DuO9G3nAizI3SkFAA

4554b3722d71SbPiI2Gx-RhbZjmuIQ

sql/mysqld.cc

+19 −8
Original line number Diff line number Diff line
@@ -2015,6 +2015,17 @@ later when used with nscd), disable LDAP in your nsswitch.conf, or use a\n\ 
mysqld that is not statically linked.\n");

#endif



  if (locked_in_memory)

  {

    fprintf(stderr, "\n\

The \"--memlock\" argument, which was enabled, uses system calls that are\n\

unreliable and unstable on some operating systems and operating-system\n\

versions (notably, some versions of Linux).  This crash could be due to use\n\

of those buggy OS calls.  You should consider whether you really need the\n\

\"--memlock\" parameter and/or consult the OS distributer about \"mlockall\"\n\

bugs.\n");

  }



  if (test_flags & TEST_CORE_ON_SIGNAL)

  {

    fprintf(stderr, "Writing a core file\n");