[EMAIL PROTECTED] said: > John Meissen said: > >I can only talk to the server if I'm the user that started it. > > > The user who launched esd must type 'esdctl unlock' to let other user > use this daemon, I think. Does it solve the problem ?
Actually, I replied too soon. No, it doesn't solve the problem. I don't run esd persistently. I try to run fairly lightweight. For instance, I use AfterStep as my window manager. Esd gets launched by the applications that are configured to use it, and only persists while it is being used. Hence, any attempt to dynamically unlock will be ineffective, since the request will be forgotten when that instance terminates. What I need is for the -promiscuous option to work as documented. I added it to /etc/esd.conf, and I can see it in the process command- line. But it doesn't work. john- ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ enlightenment-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
