| Summary: | KRFB allows only one concurrent connection | ||
|---|---|---|---|
| Product: | [Applications] krfb | Reporter: | Tomasz Chmielewski <mangoo> |
| Component: | general | Assignee: | George Goldberg <grundleborg> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | alon.barlev, grundleborg, stasnel, steven.gabel |
| Priority: | HI | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandrake RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Tomasz Chmielewski
2005-02-25 10:47:03 UTC
I removed that feature away because its relatively difficult to do with krfb's implementation. Connections are accepted by kded/kinetd, which then starts krfb. It's easy to pass a TCP connection when you start a process (just fork and take it over in the new process), but there is no easy and portable way in Unix to pass a TCP connection to a running process. *** Bug 143060 has been marked as a duplicate of this bug. *** This actually *almost* works in current krfb trunk. I can connect multiple times, but the server shuts down when one connection disconnects, forcing all the others to as well. Also, the notification item tooltip, which lists who is currently connected, only displays the most recent connection. The good news is, I reckon it won't take more than a few small adjustments to the code to make this work properly :). Upping the priority so I remember to fix this one soon. This should be working in trunk now. I haven't tested it though. Does not work for me... ever connection disconnect the previous. kde-base/krfb-4.9.3 |