Community
Participate
Working Groups
Create a new connection of type Linux, on 2nd wizard page select Server Launcher = Rexec and enter appropriate properties. Press Next, Next, Finish. Expand the files subsystem to connect. Observe "Cannot connect to daemon: Connection refused on port 4035". --> Rexec settings have not been persisted from the New Connection Wizard. Workaround: Select the files subsystem, choose Properties, and specify the Rexec server launcher there. Now it works correctly. -----------Enter bugs above this line----------- TM 2.0M5 Testing installation : eclipse-SDK-3.3M5 (I20070209-1006), cdt-4.0M5, emf-2.3M5 RSE install : RSE-SDK I20070219-1645 + discovery + efs java.runtime : Sun 1.4.2_13 os.name: : Windows XP 5.1, Service Pack 1 ------------------------------------------------ systemtype : Unix-ssh / Linux-dstore-processes targetos : Red Hat Enterprise Linux WS release 4 (Nahant Update 3) targetuname : Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux targetvm : Sun Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode) ------------------------------------------------
This works for me. Could this have been related the the new connection problems that have now been fixed?
Reproduced the issue again with I20070221-1831 on Windows. The problem is, that the wizard pages don't exchange data about the Launcher: * New Connection, Type = Linux, enter hostname, Next * Select dstore.files, Launcher, switch to Rexec, enter a server-path * Press Next * Select dstore.processes, Launcher --> Note that the Launcher is "Daemon" again It would be good to get this done for M5 if the fix involves no risk. If it seems risky, better wait for M6.
On further investigation, it works OK for me when I enter the launcher in the first page only and press Finish early enough. It looks like this is related to bug 175142 and the problem is, that the Service page for the org.eclipse.rse.subsystems.processes.shell.linux subsystem is somehow broken.
With the fix for bug 179363 the original problem is fixed, since any modification of standard settings has priority over unchanged settings: thus, if REXEC Launcher is specified on one of the pages, it will be accepted. It is still nonintuitive, though, that when REXEC launcher is selected on the first wizard page, the second wizard page still shows the Daemon launcher. This is being tracked in bug 181162 now.
Verified with I20070405-0600. Closing.
[target cleanup] 2.0 M6 was the original target milestone for this bug
