[Konversation-devel] [Bug 143245] New: pre command functionality is not enough :)

[Jakub Turski]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=143245         
           Summary: pre command functionality is not enough :)
           Product: konversation
           Version: 1.0.1
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel kde org
        ReportedBy: yacoob gmail com


Version:           1.0.1 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3.1)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17-11-generic

One possible field of application for pre command would be setting up ssh tunnel. Sadly, as it is, pre command is not enough. First of all, it is defined at identity level, while it should be defined at server level. It is launched once per each server using this identity, which leads to same tunnel being created more than once (of course port is busy, but ssh process stays). It should be either defined at server (or group of servers) level, or take parameters, such as name of the server we're connecting to, etc. The latter solution is a bit worse, because one would need to read the name of the server, and decide which tunnel to set up basing on that information - it's putting logic outside main application :) Secondly, once tunnel is launched, there's no "reaper" that can bring the tunnel down on konversation exit - ssh processes are becoming children of init, and hang there indefinitelly. Perhaps a post command? Or just launch precommand in the background, and kill it once konversation, its parent exits?

Those are my 0.02EUR :)

Regards,

KT.