Hi, I'm not sure if this has been mentioned before, I couldn't find it in the archives but I'm sure I read something about it.
The problem I'm having is on the thin clients I've setup (using the 2.6.9-ltsp-3 kernel), the first user (say, user01) logs in and gets sound from the server without a problem, if they then log out, and user02 logs in, they get the error message about not being able to connect to the sound server. I've been looking on the clients, and the esd server is still running but (I'm guessing) is denying access to the new user, presumably because the first user takes ownership of it. To confirm I've manually killed the server and re-run the rc.sound script to start it back up, as before the first user that logs in gets sound, but any after that don't. It's worth noting that if user01 logs out, then logs back in again (or even with another user inbetween) they will still get sound, which supports the idea that the esd server is being owned by the first user that connects to it. The solution would seem to be to kill the esd server on logout, but there is no way that the thin client knows when a user logs out (it's all fowarded X?) so there isn't any part of the logout script that can be editted to kill the esd daemon as the scripts run on the actual server! (afaik, anyway). Could anyone suggest a way of instructing the client to kill it's esd daemon, or an equally clever workaround? :) Thanks, James [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
