similar to: keepalive parameter on 2.0.4b

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,

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

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?

http://bugzilla.mindrot.org/show_bug.cgi?id=443 Summary: Ability to set KeepAlive time Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: danfuzz at

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:

I'm having some trouble compiling samba 2.0.4b on an 64bit HP-UX 11 system. The configure script finishes without any errors. But when I go to compile it, I get these errors: Compiling smbd/server.c (Bundled) cc: warning 480: The -O option is available only with the C/ANSI C product; ignored. cpp: "/usr/include/sys/xti.h", line 488: warning 2001: Redefinition of macro TCP_NODELAY.

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 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

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

Hi list, After a recent upgrade to Asterisk v1.4.14, my message log is now filling up with the following error messages: <-------------> [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645 determine_firstline_parts: Bad request protocol Packet --- (1 headers 0 lines) --- bitis*CLI> <--- SIP read from 82.101.62.99:5060 ---> Cirpack KeepAlive Packet <-------------> Seeing

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

Hi. Our CentOS 5.4 server just rebooted sponteneously while doing heavy I/O. There is a message in /var/log/messages just prior to reboot, kernel: Keepalive, Event:mdseve_cookie, client ping timeout Google does not turn up anything. What does this mean and how can I prevent it from happening again, please? Best, -at

Hi, we have samba 2.2.2 on solaris 2.6, in dual personality, with security=user for a netbios name, and security=server for another netbios name. The clients are mostly win2k terminal server users. In the morning some users are able to connect drives through the shares with security=server but then comes those messages in the logs : ... password server keepalive failed. password server is not

Greetings, I don't know how common an issue this is as I haven't found much in the list archives that was helpful to me, so I'm hoping for some pointers. FYI, we have samba 2.3.3a-6 running on the 2.4.18-10 kernel. There seems to be an issue with smbfs mounts at times where connectivity may be lost (e.g. Win share becomes unavailable) causing local processes such as lsof or ps,

http://bugzilla.mindrot.org/show_bug.cgi?id=763 Summary: Add Null packet keepalive option Product: Portable OpenSSH Version: 3.7p1 Platform: All URL: http://marc.theaimsgroup.com/?l=openssh-unix- dev&m=98460103932386&w=2 OS/Version: All Status: NEW Severity: enhancement

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,

On 18 Jul 99, giulioo@tiscalinet.it (Giulio Orsero) had questions about 2.0.4b: logrotate problems: [snip] > As I said, my problem was not that logrotate didn't rotate; but > thet after logrotate rotated a log smbd kept logging to the > rotated file instead of to the newly created, empty, log.smb. The > newly created log.smb remained empty forever, till I restarted > smbd.

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