Re: bin/47394: Mysql daemon does not START in boot time

[Sverre Froyen <sverre%viewmark.com@localhost>]

The following reply was made to PR bin/47394; it has been noted by GNATS.

From: Sverre Froyen <sverre%viewmark.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: martin%duskware.de@localhost
Subject: Re: bin/47394: Mysql daemon does not START in boot time
Date: Mon, 14 Jan 2013 08:44:22 -0700

 On Wed, 9 Jan 2013 09:26:46 +0100, Martin Husemann wrote:
 > On Tue, Jan 08, 2013 at 10:35:38PM -0500, Edgar Rodolfo wrote:
 >  > This is partial solution, but my purpose is that it should be fixed =
 in
 >  > the another release (6.0.x) because is a bug
 > =20
 > Unless I misunderstand something, it can not be solved in a future
 > NetBSD release, as it is not an OS bug.
 > =20
 > However, it can be fixed in the mysqld package (like Takahiro Kambe
 > suggested), or in the mysqld code.
 
 While I do not particularly care for the way mysqld_safe starts mysqld, =
 I would like to better understand the issue before I accept that this is =
 not a NetBSD bug.
 
 Without the output redirect (or the delay), mysqld segfaults when =
 started up at boot time -- perhaps related to IO handling in the rc =
 scripts. If the problem can be fixed there, i.e. the rc scripts, it =
 would make NetBSD more user friendly. If it cannot, the issue should be =
 documented. (I could not find anything obvious in the rc man pages.)
 
 Regards,
 Sverre=