Yes, you should. What do you have in your
~/.kde/share/kinetdrc and
kinetd.events files? It's been a while since I used mine, but they look like this:
Code:
$ cat ~/.kde/share/config/kinetdrc
[ListenerConfig]
enable_srvreg_krfb=true
enable_srvreg_krfb_httpd=true
enabled_expiration_krfb=2935093,2,28,0,0,0
enabled_expiration_krfb_httpd=2935093,2,28,0,0,0
enabled_krfb=true
enabled_krfb_httpd=true
$ cat ~/.kde/share/config/kinetd.eventsrc
[IncomingConnection]
commandline=
logfile=
presentation=4
soundfile=
[ProcessFailed]
commandline=
logfile=
presentation=4
soundfile=
I'd suggest setting up a few invitations on you system, and looking at how the settings change (especially the
expiration ones) to see if you could just leave some open invitations for your clients on your system. (
CAUTION: This may be a security risk. Try to limit access to the port (
:5000, I think) to known IP addresses in your firewall.[/b])
I notice that there is a
--kinetd option listed when you do a
$ krfb --help-all command, but -- as you probably know -- the KDE Krfb help file is somewhat less than complete, so I've no idea how it might be used.
Another option, again not well documented is the
--waitforwm one. I don't know what the
WM_NET protocol for which that instructs
krfb to wait is, but you might try it from a client system to see if it tries to open a window on the client system using the local window manager.
Edit: Have you looked at
this HOW-TO?