|Keep It Simple, Stupid|
Re^3: Remote ptkdb behind firewallby oko1 (Deacon)
|on Feb 19, 2012 at 18:38 UTC||Need Help??|
AFAIK, there's no functional difference between a BEGIN block with and without "sub".
Oh - that's a new one on me. :) Thanks!
As for the OP's problem, the issue presumably is that the www-data user doesn't have a cookie that would allow authentication with the X server.
Mmm... maybe. Or it might require having the remote X server listen for the connection on 6000+; depends on how 'ptkdb' is written, I would think. Most Linux distros these days run X with the '-nolisten tcp' option, which is quite the pain to disable (I needed to do it a while back, in similar circumstances); at that point, 'xhost hostname' allows communication from the other host, etc. As I'm sure you're aware, though, this has various security implications.
(Ah, good old X, with its annoyingly-high level of access to root privileges and infuriatingly-arcane protocols. Always such fun. :)
Update: I just tried it out. On my machines (Ubuntu "Oneiric Ocelot", both ends), setting the cookie didn't help; turning off '-nolisten tcp' and running 'xhost otherhost' popped up that 'ptkdb' window right away.
Actually, I'm not very happy with that. When I get a little more time (I've got to run off to my boat and do a bunch of maintenance), I'm going to see if I can force it to work in a more reasonable way - i.e., the way you suggested - or figure out how to patch ptkdb so it works with that model, if possible.
-- I hate storms, but calms undermine my spirits. -- Bernard Moitessier, "The Long Way"