Date: Thu, 31 Oct 2002 10:19:38 -0500 (EST) From: Adrian Filipi-Martin <adrian@ubergeeks.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/44784: mysqld looses track of its working directory Message-ID: <200210311519.g9VFJcNc072699@mail.ubergeeks.com>
next in thread | raw e-mail | index | archive | help
>Number: 44784 >Category: ports >Synopsis: mysqld looses track of its working directory >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 31 07:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Adrian Filipi-Martin >Release: FreeBSD 4.7-STABLE i386 >Organization: Ubergeeks Consulting >Environment: System: FreeBSD lorax.ubergeeks.com 4.7-STABLE FreeBSD 4.7-STABLE #31: Thu Sep 22 14:22:46 EDT 2002 root@lorax.ubergeeks.com:/usr/obj/usr/src/sys/LORAX i386 /usr/ports from 10/22/02. >Description: realpath(3) is not thread-safe. As a result one thread in mysqld can cause another to get "lost" in a directory other than the top level directory of the DB. mysqld often gets stuck with its current working directory in /var/tmp with "vi.recover" as the only "valid" database. This causes the server to believe that it has no other databases and become useless until it is restarted. >How-To-Repeat: This scenario is not easy to trigger. Log lived transactions/threads, such as are present when using MySQL's replication facilities, seem to be more susceptible to this problem. If USENET or Goole are searched, more examples of users experincing this problem can be found. >Fix: realpath(3) is similarly broken on other platforms. MySQL has a build option HAVE_BROKEN_REALPATH that works around this problem. Building the port as follows is enough to correct the problem. make CFLAGS=-DHAVE_BROKEN_REALPATH >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210311519.g9VFJcNc072699>