I'm logged (as root) when I start my daemons and I remaining logged to monitor the log produced (I use the same shell inside I've launched daemon).
My detailed problem is:
a) I'm building a Visually Impaired Guide Enhanced Robot
b) I've a lot of asynchronous signals I receive from external devices
c) I need an asynchronous engine to manage that signals and drives output commands
So... As preliminary step I have a GPS module attached to my notebook and I successful receive GPS attach event and coordinates. Then I call geonames.org Web Service to compute a reverse geocoding and obtain the current address (and all is correctly logged).
When I build the text to be spoken and I pass it to speechdispatcher through a timer event, speechdispatcher really speak my text (I receive the end speak event), but I no hear any sound (and this only if program is running as daemon, as normal process all works fine).
So, if I understand what you mean, you're telling me, to no call speechdispatcher directly but move the code I use to make speechdispatecher working inside a different process called by daemon.
I think I'll be able to do so. But I don't understand the difference between calling directly speechdispatcher or using another process. It's only a SW layer that I interpose between my daemon and speechdispatcher. Do you think it could solve my problem since the calling context is changed?
Thanks a lot,
I put here my complete source code: