1. 02 Dec, 2002 1 commit
  2. 30 Nov, 2002 2 commits
  3. 29 Nov, 2002 5 commits
  4. 28 Nov, 2002 5 commits
  5. 27 Nov, 2002 1 commit
  6. 26 Nov, 2002 2 commits
  7. 25 Nov, 2002 2 commits
  8. 24 Nov, 2002 6 commits
  9. 23 Nov, 2002 3 commits
    • Sinisa@sinisa.nasamreza.org's avatar
      FreeBSD patch by Jeremy Zawodny. · aa1c10e7
      Sinisa@sinisa.nasamreza.org authored
      His explanation:
      
       The socket on which MySQL listens for new connections on a blocking
        socket most of the time but is set to non-blocking during the
        accept() of the new connection.  Due to a bug in the kernel, the new
        socket returned by accept() is a blocking socket but returns the
        O_NONBLOCK flag when queried via fcntl(F_GETFL).  That is, the file
        descriptor and the underlying socket don't agree on the blocking
        mode.
      
        Since MySQL determines via fcntl(F_GETFL) that the socket is
        non-blocking, it expects the first read() in my_real_read to not
        block, so it doesn't enable the timeout alarm.  However, the read
        does block, and thus there's no timeout alarm.  The thread kill
        (which relies on rescheduling the timeout alarm) also does not work
        as a consequence.
      
      The bug shows itself if you build MySQL with LinuxThreads support
      (needed for SMP on FreeBSD).  Issuing a KILL command in MySQL won't be
      "noticed" by the "killed" thread until it runs another query--that
      makes KILL pretty useless.  And the wait_timeout doesn't work either.
      aa1c10e7
    • Sinisa@sinisa.nasamreza.org's avatar
      Merge sinisa@work.mysql.com:/home/bk/mysql-4.0 · a96d3ca9
      Sinisa@sinisa.nasamreza.org authored
      into sinisa.nasamreza.org:/mnt/work/mysql-4.0
      a96d3ca9
    • Sinisa@sinisa.nasamreza.org's avatar
      db264ac8
  10. 22 Nov, 2002 8 commits
  11. 21 Nov, 2002 5 commits