Bug 92 - Feature: -f -f, like -f, but fork() after port/display/agent open
Summary: Feature: -f -f, like -f, but fork() after port/display/agent open
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: -current
Hardware: All All
: P2 enhancement
Assignee: OpenSSH Bugzilla mailing list
URL: http://marc.theaimsgroup.com/?l=opens...
Keywords:
Depends on:
Blocks: V_5_1
  Show dependency treegraph
 
Reported: 2002-02-02 05:38 AEDT by Nicolas Williams
Modified: 2008-07-22 12:06 AEST (History)
1 user (show)

See Also:


Attachments
feature patch for -f -f (3.97 KB, patch)
2002-02-02 06:23 AEDT, Nicolas Williams
no flags Details | Diff
delay fork when ExitOnForwardFailure set (2.04 KB, patch)
2008-06-29 18:57 AEST, Damien Miller
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Williams 2002-02-02 05:38:59 AEDT
New ssh option, "-f -f", like "-f", but fork() after the first successful
forwarded port/display/agent channel open.

The idea is that a successful forwarded port/display/agent channel open
implies that the remote command started successfully and can report
errors in some manner other than by writing to stderr or exiting with
a non-zero exit code. So that is a great time for ssh to fork() off.

Also see new forkoff() function added to clientloop.c - it correctly,
I think, closes the session channel.
Comment 1 Nicolas Williams 2002-02-02 06:23:26 AEDT
Created attachment 15 [details]
feature patch for -f -f
Comment 2 Damien Miller 2008-06-29 18:57:03 AEST
Created attachment 1536 [details]
delay fork when ExitOnForwardFailure set

This is quite easy now that we have proper request callback queues, but I don't think we need a funny non-idempotent option for it. This patch makes -f wait until after the rfwd replies have been received if ExitOnForwardFailure=yes.
Comment 3 Damien Miller 2008-06-29 18:57:38 AEST
Put this on the list for 5.1
Comment 4 Damien Miller 2008-07-02 23:49:08 AEST
fixed - will be in openssh-5.1 (wasn't it worth the wait?)
Comment 5 Damien Miller 2008-07-22 12:06:30 AEST
Mass update RESOLVED->CLOSED after release of openssh-5.1