over the last year on several occasions, i've seen folks spend a couple
of hours debugging this option and coming to the same results ... it
times out weather it's being used or not.
the -a timeout option is just plain broken.
would it be possible to either disable this option entirely, or at
According to
URL:
https://sourceforge.net/tracker/index.php?func=detailaid=819235group_id=13229atid=113229
and the tcp(7) manual page, the nbd server should disconnect the
connection after 2 hours 11 minutes if the client fail to respond to
tcp keepalive requests. The keepalive feature was
the workaround is just to have the machine running an nbd-client make
nbd accesses periodically just to keep the connection alive... but
that's kind of ugly.
I have tried this.
basicaly i ran nbd-server using -a 600 so it would timeout after 10 minutes
The nbd-client connects and working,
On Sat, Feb 03, 2007 at 11:54:49AM -0800, Vagrant Cascadian wrote:
Package: nbd-server
Version: 1:2.8.7-3
Severity: normal
when using nbd-server with the -a timeout option, it will often
disconnect running nbd-client instances that have merely been inactive
for a while. it would be much,
On Sun, Feb 04, 2007 at 08:45:15PM +0100, Wouter Verhelst wrote:
On Sat, Feb 03, 2007 at 11:54:49AM -0800, Vagrant Cascadian wrote:
when using nbd-server with the -a timeout option, it will often
disconnect running nbd-client instances that have merely been inactive
for a while. it would be
Package: nbd-server
Version: 1:2.8.7-3
Severity: normal
when using nbd-server with the -a timeout option, it will often
disconnect running nbd-client instances that have merely been inactive
for a while. it would be much, much more useful if it implemented some
sort of ping to determine if the
6 matches
Mail list logo
