Am Thu, 31 Aug 2000 schrieb Stefan Westerfeld:
> I see that the patch is already applied, however I think that the whole
> reconnect soundserver thing might be a problem sometimes: Suppose you have
> quite a lot of notifications (syssound) but no working server (no
> soundcard).
>
> However for each notification, knotify will now try to reconnect to the
> soundserver, block for about eight seconds, and then come back. This might
> lead to having some important notifications pop up really really very late,
> as knotify is busy reconnecting all the time.
>
> The patch impacted this because it tries to reconnect on .isNull now, too,
> which means that even if it is always unsuccessful, it will try to
> reconnect on each event.

This was meant to be like that because otherwise many people who use kernel 
2.4 won't get any sound event ever because artsd isn't launched on login. But 
you're right this will lead to problems if there is no artsd running at all.
What's about reducing the 8 seconds to only one try to connect? Is there a 
reason for those 8 seconds?

Bye
  Schimmi
_______________________________________________
Kde-multimedia mailing list
Kde-multimedia@master.kde.org
http://master.kde.org/mailman/listinfo/kde-multimedia