Hi Sebastian!
You wrote:
> > > Hmm... I cannot reproduce this. It works fine on all machines I'm running
> > > collectd on. Please note that it might take some time (a couple of
> > > seconds)
> > > for collectd to shut down cleanly. Could you please verify this?
> >
> > Ah, that indeed seems to be the case. It's a bit confusing though. Are
> > you sure this isn't going to lead to weird race problems?
>
> I cannot think of any race conditions. Have you run into any problems so far?
> What kind of problems are you thinking about?
Well, maybe if the user wants to restart the daemon before the old one
is exited? Won't the port still be taken then?
> The shutdown time should have been decreased a fair amount in version 3.10.4.
> Can you estimate that amount of time it takes for you? I'm going to
> investigate if it should be further decreased. Any other opinions on this?
Actually, since I set up collectd on my machines, I've never noticed it
anymore. It's jsut when you tinker with the config files and start and
stop the daemon lots of time that it gets noticable.
As the behaviour is not what most uses would expect when running an
init.d "stop" script, maybe it would be better to just avoid it at all
by letting the init script wait for the daemon to exit? Squid seem to
do it like that...
Anyway, not a really big issue..
Greetings,
Bas.
--
+--------------------------------------------------------------+
| Bas Zoetekouw | Sweet day, so cool, so calm, so bright, |
|--------------------| The bridall of the earth and skie: |
| [EMAIL PROTECTED] | The dew shall weep thy fall tonight; |
+--------------------| For thou must die. |
+-----------------------------------------+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
