Re: Daemontool-izing MySQL

Unfortunately, I am fairly tied to MySQL.  Currently this is the
database for all of my IDS, syslog files, circuit tracking, IP
tracking, etc.

The structure used within the different databases is sufficiently
diverse that porting is a task that I currently do not have the cycles
to attempt.

And I had tried the scripts from the smarden.org site (both the
"Linux" script and the "Sun" script), but for whatever reason,
although MySQL starts, it continues to start instance after instance
until the database actually starts throwing errors and corrupting
itself.

The svc calls to the script also fail to close the database and stop
all the spawned processes.

From my searches on Google, the problem appears to be in the way the
mysqld_safe script starts, as it is expecting to background itself and
release it primary PID.  With svc that presents a problem.
Direct e-mails to those who claimed to have found a solution have gone
unanswered as of yet, thus prompting my e-mails to this list since
some of the claimants were allegedly going to post here with their
solution.

Again, thanks to all that have been trying to help.

-- 
Ed Vázquez

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don't be irreplaceable.
If you can't be replaced, you can't be promoted.

On Thu, 14 Aug 2003, Bruno Wolff III wrote:

> If you are not specifically tied to MySQL, you could run postgres instead.
> It is very easy to daemonize as it writes its log information to
> standard output by default. It also responds reasonably to svc -d .
>