Displaying 20 results from an estimated 900 matches similar to: "[PATCH] Connect timeout"
2001 Nov 17
0
[PATCH] Connect timeout
The attached patch adds a new 'ConnectTimeout' option (man page updated
in patch) to avoid wasting time when the target host is down. I needed that
because I was using rsync/rdist over ssh for massive files update and the
default connect() took too long for my purpose.
The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX
on Linux, Solaris and HP-UX without
2002 Apr 03
1
[PATCH] connect() timeout
Here is a version of this widely used patch specific for OpenSSH 3.1p1,
as it is still not in the main tree (perhap one day...)
The patch avoids spending too much time when doing an ssh()/scp() on a
down host, as it does not depend off the default TCP timeout used
by connect().
Patch was tested on Linux, Solaris and HP-UX.
The patch can also be found on:
2002 May 22
0
[PATCH] connect() timeout
Here are the new versions of this widely used patch for OpenSSH 3.2.2p1
and 3.2.3p1.
The patch avoids waiting to long when using ssh() or scp() on a down host,
it is usefull when you have to update many hosts via rsync or rdist themselves
relying upon ssh(). It enables a new option 'ConnectTimeout' to control
exactly the timeout value, so that it can be used even on slow links.
These
2003 Apr 15
0
Connect timeout patch
This patch avoids spending too much time during connect() when doing an
ssh()/scp() on a down host. It uses a new client option called
ConnectTimeout and is useful for rsync or rdist commands using ssh().
See http://bugzilla.mindrot.org/show_bug.cgi?id=207 for detailled info.
-------------- next part --------------
--- openssh-3.6.1p1/readconf.c.ORIG Tue Apr 15 23:06:30 2003
+++
2002 Oct 17
0
[PATCH] connect() timeout for OpenSSH-3.5p1
Here is the version of this patch for the last portable version of
OpenSSH (3.5p1), as it is not included in the main tree.
The patch avoids waiting to long when using ssh() or scp() on a down host,
it is usefull when you have to update many hosts via rsync or rdist themselves
relying upon ssh(). It enables a new option 'ConnectTimeout' to control
exactly the timeout value, so that it can
2017 Jan 12
3
proposed change to ssh_connect_direct()
On Sat, Jan 7, 2017 at 2:30 PM, Peter Moody <mindrot at hda3.com> wrote:
> so I spent a bit of time looking at this and it seems like the only
> way to go, at least if I want to keep it in ssh_connect_direct(), is
> to use pthreads. further, it seems like getting that accepted is
> something of a long shot:
Sorry, pthreads is a non-starter.
I would have thought that using
2000 Jun 06
0
connection timeout
Attached is a patch which adds a ConnectionTimeout option, and corrects
the ConnectionAttempts documentation.
Previously, ssh would try to make a connection ConnectionAttempts times,
sleeping 1 second between tries. But each connection attempt could take a
very long time to fail if the packets die before the get to the host. So
if ssh is being run in a script or what-have-you, it might be
2000 Nov 14
1
[PATCH] Added option 'RetryDelay'
Being rather aggrevated when testing at the enforced 1 second
delay between each connection attempt and the useless 1 second delay
done after all connection attempts have failed I wrote a patch to make
the number of seconds delayed between each connection attempt
configurable.
Stephen
-------------- next part --------------
diff -u --recursive openssh-2.3.0p1/ChangeLog
2009 Jan 07
2
Question about documentation for ConnectTimeout
Hello OpenSSH folks,
This was a really minor knit, but I noted while I was developing a
pexpect module for ssh that setting ConnectTimeout to 0 in the options
to ssh sets the login timeout to infinite time.
I was wondering whether or not this was a documentation bug and/or
potential clarification that could to be made, or if this was a
software bug that needs to be fixed. I don't see
2018 Feb 23
7
RFC 8305 Happy Eyeballs in OpenSSH
Hello,
I use hosts that are dual stack configured (IPv4 and IPv6) and it
happens that connectivity through one or the other is broken and
timeouts. In these case connection to the SSH server can take quite some
time as ssh waits for the first address to timeout before trying the
next.
So I gave a stab at implementing RFC 8305. This patch implements part of
it in sshconnect.c.
* It does not do
2013 Oct 07
4
Feature request: FQDN Host match
Hello!
I'm hoping that Gmail won't HTML format this mail so that I'll get flamed :)
Anyway, my question relates to ssh_config. The problem I find is that
the Host pattern is only applied to the argument given on the command
line, as outlined in the man page:
"The host is the hostname argument given on the command line (i.e. the
name is not converted to a canonicalized host name
2010 Nov 28
2
[PATCH] Use canonical hostname for DNS SSHFP lookup
In the current implementation, ssh always uses the hostname supplied by
the user directly for the SSHFP DNS record lookup. This causes problems
when using the domain search path, e.g. I have "search example.com" in my
resolv.conf and then do a "ssh host", I will connect to host.example.com,
but ssh will query the DNS for an SSHFP record of "host.", not
2002 Jan 27
0
[PATCH] Add an exit delay to Openssh-3.0.2p1 for use in tunneling
Here is a patch to implement an exit delay in OpenSSH-3.0.2p1,
proposed by John Hardin. This is his description of the feature:
New option for OpenSSH: Delay before exit.
Command line option: -S delay
Config file option: sleep {delay}
Purpose: Wait the specified number of seconds after last traffic before
dropping the connection and exiting. If ports are forwarded, this causes
the ssh client
2004 Mar 26
2
Patch for login exchange timeout
Here's a quick patch that adds a timeout (value set
from the connection timeout config parameter) for
identification exchange. The situation that this fixes
is the one where the sshd has a connection open (so
you can make a TCP connection) but does not put up a
banner (e.g. when the disk has crashed or when file
descriptors are exhausted on a machine). Sounds
unusual, but this happens with
2017 Feb 03
5
[PATCH 0/5] Support socket activation in virt-p2v.
As the subject says, support socket activation in virt-p2v.
I have added upstream support for socket activation to nbdkit already:
https://github.com/libguestfs/nbdkit/commit/7ff39d028c6359f5c0925ed2cf4a2c4c751af2e4
I posted a patch for qemu-nbd, still waiting on more reviews for that
one:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg427246.html
I tested this against old and new qemu
2016 Oct 20
5
-e escape rule
Hello,
I'm using Ruby's Shellwords module, which generates a string from an
array, suitable for shell evaluation.
Ruby's implementation prefers escaping whitespace with a backslash
rather than quotes. However, this appears to cause some kind of issue
in Rsync when it computes argv from -e option.
Here is an example command generated by some Ruby code:
rsync --archive --stats -e
2014 Dec 15
2
[PATCH v2 0/1] p2v: avoid connecting to ourself while probing qemu-nbd
Changes since v1:
- Set probing source port to be nbd_local_port+1 instead of always
using 50124 to deal with multi-disk scenario.
- Set SO_REUSEADDR on client socket to avoid issues with old
connections in TIME_WAIT.
I've been running this for a few hours now using the updated
multi-disk test and haven't seen any problems.
2017 Mar 06
7
[PATCH 0/6] Various Coverity fixes #2
Hi,
this patch series fixes few more issues discovered by Coverity.
Thanks,
Pino Toscano (6):
tail: check the return value pf guestfs_set_pgroup
daemon: btrfs: check end_stringsbuf return values everywhere
java: use cleanup handlers for structs (lists) as return values
lib: qemu: improve handling of FILE*
p2v: check more return values
p2v: fix possible close(-1) issue
cat/tail.c
2009 Dec 24
3
ConnectTimeout=2 not working for me
Hi all,
I have somewhat a strange problem that I could not figure out, maybe someone
here can lelp.
I have a script that uses scp to distribute files to many servers, I use '-o
BatchMode=yes -o ConnectTimeout=2 options so the scp will not get stuck if
something is wrong with the remote host.
If the remote host is down (non-pingable) or sshd is down the timeout option
works and the scp
2002 Jun 11
4
ssh setuid changes.
Ok, I'm doing a heads up here.
I just applied:
- markus at cvs.openbsd.org 2002/06/11 04:14:26
[ssh.c sshconnect.c sshconnect.h]
no longer use uidswap.[ch] from the ssh client
run less code with euid==0 if ssh is installed setuid root
just switch the euid, don't switch the complete set of groups
(this is only needed by sshd). ok provos@
A few comments about