Joerg Bruehe wrote:
Yes, it does announce.
I wrote "any external event ... that Windows *would* monitor"
(emphasis added): Does the Windows ServiceManager really know which
file to monitor for which entry to announce the service as "running" ?
see below.
in practice we find the service co
Hi Les, all,
sorry - I attended to other things more than to this thread.
Les Schaffer wrote:
Joerg Bruehe wrote:
I assume Windows reports the status as "running" when the process(es)
got started, but that doesn't necessary imply they have passed their
own initialization / startup phase.
Joerg Bruehe wrote:
I assume Windows reports the status as "running" when the process(es)
got started, but that doesn't necessary imply they have passed their
own initialization / startup phase.
I doubt there is any external event (say, a file creation or some
such) that Windows would monit
Hi Les, all !
Les Schaffer schrieb:
[[...]]
perhaps i wasn't clear earlier. we checked the logs, and we see that
Innodb is started and accepting connections sometimes 1-6 seconds AFTER
we see the Windows ServiceManager report that the MySQL service is in
state SERVICE_RUNNING.
we had thou
Sebastian Mendel wrote:
did you take a look add the MySQL log?
there you can see what MySQL is doing, with times
perhaps i wasn't clear earlier. we checked the logs, and we see that
Innodb is started and accepting connections sometimes 1-6 seconds AFTER
we see the Windows ServiceManager repo
>-Original Message-
>From: Les Schaffer [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, June 04, 2008 9:23 PM
>To: mysql@lists.mysql.com
>Subject: mysqld-nt Windows service: delay btwn svc running and accepting
>conx
>
>We are having a small technical glitch about which we would like to have
>s
Les Schaffer schrieb:
We are having a small technical glitch about which we would like to have
some insight:
our application needs to start mysqld-nt as a Windows service after
which we fairly quickly try to make connections to the Server. we are
using the python wrappers, MySQLdb, and we suc