On 12/23/12 02:27 +0100, Fabien C. wrote:
Hello,
This is absolutely not an acceptable fix for this bug. A 'sleep' only
reduces the frequency of a race, it does not eliminate it.
Yes, I totally agree, it would only be a dirty workaround. However, when
the issue is complicated to fix, I think that reducing problem frequency
in the meanwhile is a good thing, especially when it takes 2 minutes to
be done.
Then, we can try to find and correct the *source* of the problem, fixing
it and remove the ugly workaround.
Please don't get suckered in to this form of thinking. I have a proprietary
service at work that takes > 20 minutes to start up, on a redhat system.
It's Java based, and has several different processes that it starts up.
It's solution for process interdependencies is to sleep 60 seconds,
or 300 seconds, or X seconds before starting the next process.
Every release seems to get a slower startup time too. I suspect the
developers have found corner cases and received support calls where some
system condition caused something to not get started within that expected
sleep window, and they just increase the sleep time.
I have a gripe with systems that don't handle ldap server (or networking)
failure properly, and require a restart of that process in the event an
ldap connection times out.
Bind is also at fault here for not taking such conditions into account.
--
Dan White
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
