Re: Short test report (testing sound on daily build)

[Petter Reinholdtsen <pere@hungry.com>]

[Ole-Anders Andreassen]
> Installed daily from 22.feb (ltspserver)

Thank you for your test report.

To test sound, it should be enough with a lts.conf file like this:

  [default]
    SOUND              = Y

>  Conclusion
>  This is strange...... :-?

Not the way I read it.  When a thin client boots, esd is started and
is accepting connections from anyone.  The first user to connect
get/set some key and store it in ~/.esd_key, and the esd server
"locks" to this key.  After this, only user with the key kan play
sound on the given client.

Logging out the user do not reset esd running on the client, so no
other user is able to play sound.  You can test this by copying the
.esd_key file around to the other users and see if they can play sound
on the given client.

This system make sure no one else can play and record music on other
users thin client.  This is good.  But we need to make sure esd is
reset to accept new connections when the user log out.

I see two possible fixes for this.  One is to use 'esdctl unlock' to
unlock the esd server.  Not sure what this actually do, but was told
on IRC yesterday that it allowed others to connect to esd.  If that is
the case, it might solve this problem.

Another solution is to send SIGHUP to esd when the user logs out.
According to Klaus Ade, this resets esd and make it ready to accept
new users.

One problem I see with esd is that it is only possible for one user to
use sound at one thin client at the time.  If the same user log into
another thin client, ~/.esd_key will be overwritten with the key for
the new client, and sound will stopp working with the old client.

Perhaps nas solves this issue?  I do not know.

Anyway, thank you very much for the test report.  It make sense
now. :)