[bug #22351] GDNC not starting properly on some systems.

[Yavor Doganov]

Follow-up Comment #9, bug #22351 (project gnustep):

But this happens at a time when gdnc is either not started or is
non-functional, so it is safe to assume that no such connections exist.  Isn't
it so?  I may be totally wrong, I don't understand the code very well.

Here's how I've been able to trigger this bug, although not reliably (as I
said I cannot reproduce with my patch, whether right or wrong -- and I
certainly don't claim it's right):

1. Kill all daemons as suggested in the original submission.
2. Start an app (Ink, Preferences) that would lead to gdnc launching.
3. Kill the app, so that the nameserver database remains (quiting the app in
a normal way should usually clean the database).
4. Kill gdnc.
5. Start the app again.

(Repeat steps 2-4 if the bug doesn't show yet.)

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?22351>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/