I said:
> 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.
In fact, it's even worse - it appears to have exactly the opposite effect.
Am I reading the man page wrong?
If I start
[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 th
[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 ?
I swear I tried that before. OK, maybe I didn't. :-/
John Meissen a écrit :
A long time, in a version far, far away (circa 2001), I could use
esdctl to pause/resume esd and it didn't matter what user I was.
Fast-forward to a more recent version (Mandrake 10.0 release), and
even though the permissions on the socket are 777 I can only talk
to the ser
A long time, in a version far, far away (circa 2001), I could use
esdctl to pause/resume esd and it didn't matter what user I was.
Fast-forward to a more recent version (Mandrake 10.0 release), and
even though the permissions on the socket are 777 I can only talk
to the server if I'm the user th
