similar to: [Bug 443] New: Ability to set KeepAlive time

http://bugzilla.mindrot.org/show_bug.cgi?id=443 ------- Additional Comments From dtucker at zip.com.au 2002-11-25 14:37 ------- The "KeepAlive" option enables TCP_KEEPALIVE on the socket which uses a system-wide setting (normally 2 hours according to Stevens.) There is a "Heartbeat" patch for openssh which does what you want, see

http://bugzilla.mindrot.org/show_bug.cgi?id=443 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From djm at mindrot.org 2003-01-03 14:58

I have attached a patch which adds null packet keepalive functionality to the client. This patch is made against the current CVS tree as of 3/14/01. Please consider this patch for inclusion in the OpenSSH main tree. This patch is based upon and includes code from the Chris Lightfoot (chris at ex-parrot.com) patch posted 2/23. The original patch from Chris is at:

Hi folks, I have a couple of observations about NetBIOS keepalive handling in Samba, in case anyone is interested. I came across a few oddities when investigating why some of our Samba servers were logging: lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Broken pipe type errors on a very frequent and regular basis. We have a number of Solaris 2.6 machines,

I mentioned this problem in a previous post (in November). This time I'm including a patch. Version: OpenSSH_2.3.0p1 Keywords: setsockopt keepalive hang masquerade interactive Symptom: For protocol 2, socket options (especially keepalive) are not being properly set for OpenSSH_2.3.0p1, even when request in the config files. Furthermore (for either protocol), keepalive is only set for

On Tue, Nov 01, 2016 at 05:09:34PM -0700, Jeremy Allison via samba wrote: > On Tue, Nov 01, 2016 at 05:16:47PM -0500, Ed Siefker via samba wrote: > > My expectations are probably wrong, but I had to manually kill a process > > to unlock a file when I think it should have killed itself. > > > > I have deadtime set to 15 and keepalive at default (300). I opened a file on

I'm sending this only to openssh-unix-dev at mindrot.org (since I'm using the ported version of OpenSSH) and not to openssh at openssh.com, even though I believe this to be a general problem. Please advise if you think I should redirect this to the other mailing list. Version: OpenSSH_2.2.0p1 Keywords: setsockopt keepalive hang masquerade Symptom: For protocol 2, socket options

Grandstream GXP-2000 with firmware 1.1.4.18 (beta) fixes an issue where the phone did not send rtp keepalives when on mute (resulting in disconnect from tech support hold and concalls) A side effect seems to be that Asterisk pops the following warning on the console... Jul 26 14:06:35 WARNING[31654]: rtp.c:463 ast_rtp_read: RTP Read too short Grandstream say they are not sure what it is but

https://bugzilla.mindrot.org/show_bug.cgi?id=1404 Summary: Make keepalive work properly with Cisco PIX/ASA boxes Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo:

Hi, I've got a problem with rtp keepalives. I'm using basically the same config on 2 hosts, but one of them sends rtp comfort noise when it's on hold, the other doesn't. The only difference I can think of now is that one of the machines is multihomed, but that might be unrelated. rtpkeepalive is set to 2 and I can confirm is by doing `sip show settings`. I've tried all

Need SIP KEEPALIVES in Asterisk, but QUALIFY won't presently work for you (due to it's channel disabling behavior)? Someone posted on the list that they would like to split "keepalives" and "qualify" into different features. Sounds like a good plan, but until that is done you can turn "qualify=" into a keepalive mechanism, without disabling your channels.

The default for the keepalive param in 2.0.4b is 300 although the docs. suggest that the default is 0. Does anyone know why the default changed? I need to change the keepalive value to 0 as I have some users connecting via isdn and this keepalive setting will initiate an undesired phone call. I have 100+ users on the local LAN connecting to samba on HP-UX 11 and have not experience any problems

The attached patch adds an option (off by default to preserve current behavior) to set a timeout on the select() statement that waits for input in clientloop.c. This fixes a timeout issue for me (explained below) and probably also fixes the timeouts mentioned in last month's thread "Idle time out". The patch is also available by http from:

Hi everyone, I've had instances where qemu-kvm process dies and become a zombie. At that state, libvirtd reports the instance to be running and I can't restart the VM because libvirtd fails to kill the qemu-kvm process. Finding the root cause of that is a topic for another day. I also see this line in logs: Jun 15 13:36:57 d12566 libvirtd: 10424: warning : virKeepAliveTimerInternal:156 :

I'm not sure keepalive is working the way I think it's supposed to. Here's my test. I've got a large file (approx 1 gig) on the rsync server, and I append a character on the end to make it slightly different. I fire up rsync on the client side and everything works fine until I hit the timeout value. I have this problems when I have a timeout of below 90 seconds. I've tried

My expectations are probably wrong, but I had to manually kill a process to unlock a file when I think it should have killed itself. I have deadtime set to 15 and keepalive at default (300). I opened a file on my server in Excel, then shut down the machine. Hours later someone tells me the file is locked. Shouldn't keepalive have detected that the machine was off in 5 minutes?

Qualify=yes will send a SIP OPTIONS periodically and keep the NAT open, if you use 1 to 1 NAT (versus PAT where it is "many to one NAT") it will work because port 5060 on the private address will still be port 5060 on the public address. With PAT the port could be anything over 1024, but usually much higher, and the originator will send to port 5060, which your NAT router will drop.

I have set /etc/ssh/sshd_config with: KeepAlive yes ClientAliveInterval 3 However, no KeepAlive type messages seem to be sent. I've verified this by looking at the network lights, which don't flicker every 3 seconds. I am attempting to keep interactive ssh sessions alive longer. If don't type anything for about 2 minutes, the sessions close. If I run a "idle"

Hi! I am about to migrate a perdition-based IMAP/POP3 proxy to Dovecot. Unfortunately some users are behind a firewall/NAT setup which throws away seemingly idle TCP connections sooner than the established default of 24 hours (more likely after 30 minutes ...) resulting in all kinds of weird client behavior. And unfortunately? this firewall/NAT setup is outside of my control and I have no means

Thanks to Robin and William for their keepalive scripting fu. Icecast/IceS are very crashy, and this script has worked pretty flawlessly for me. I also added some stuff to build a list of the last ten songs played. I'm using the version of the script that checks in the stats.log file for the source every two minutes. While it's doing that, it also figures out the currently playing song,