3 Apr
2011
3 Apr
'11
7:13 a.m.
I wrote:
After running yackage -l, I cannot connect to it even directly from localhost. I get the message: This Yackage server only talks to local clients
Michael Snoyman wrote:
...it doesn't sound like your problem is caused by the mis-behaving Yackage code: it *should* give you a "permission denied" error message. Does the connection work if you just run yackage normally, i.e. without -l?
Yes, as a work-around I'm running it without -l, with the firewall set to block incoming connections to the port. It's working fine that way. Thanks, Yitz