search for: tcp_keepalive

...machine/container/VM running the brick - physically pulling out the network cable Basically all those different scenarios where TCP/IP doesn't get a chance to inform the other end that it is going down. Note that some of the scenarios of ungraceful network shutdown can be identified using TCP_KEEPALIVE and TCP_USERTIMEOUT [1]. However, at the time when heartbeat mechanism was introduced in Glusterfs, TCP_KEEPALIVE couldn't identify all the ungraceful network shutdown scenarios and TCP_USER_TIMEOUT was yet to be implemented in Linux kernel. One scenario which TCP_KEEPALIVE could identify was t...

...e brick > - physically pulling out the network cable > Basically all those different scenarios where TCP/IP doesn't get a chance > to inform the other end that it is going down. Note that some of the > scenarios of ungraceful network shutdown can be identified using > TCP_KEEPALIVE and TCP_USERTIMEOUT [1]. However, at the time when heartbeat > mechanism was introduced in Glusterfs, TCP_KEEPALIVE couldn't identify all > the ungraceful network shutdown scenarios and TCP_USER_TIMEOUT was yet to > be implemented in Linux kernel. One scenario which TCP_KEEPALIVE...

Hi, I have a question regarding the "ping-timeout" option. I have been researching its purpose for a few days and it is not completely clear to me. Especially that it is apparently strongly encouraged by the Gluster community not to change or at least decrease this value! Assuming that I set ping-timeout to 10 seconds (instead of the default 42) this would mean that if I have a network

...shed 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 of correcting this (in my opinion) flawed configuration. Now, with perdition I was able to use the --tcp_keepalive option which totally solved the mentioned weird client behavior. My question is: does Dovecot2 use TCP-Keepalive on its sockets per default or do I need to enable it some way I have not yet discovered? The manual and wiki only talk about "keepalive" in connection with the IMAP protocol...

...UC 1 0 vr0 192.168.80.100 link#1 UHLW 1 0 vr0 /etc/rc.conf contains the following lines, among others: ----------------------------------------- hostname="blah.server.net" tcp_extensions="NO" log_in_vain="NO" tcp_keepalive="NO" network_interfaces="auto" ifconfig_lo0="inet 127.0.0.1" ifconfig_vr0="inet 192.168.80.222 netmask 255.255.255.0" defaultrouter="192.168.80.100" gateway_enable="NO" I also tried adding " media auto" in the ifconfig_vr0 above...

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://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html ------- You are receiving this mail because: ------- You a...

...ript_renew; +extern const char *cainfo; +extern const char *capath; +extern char *cookie; +extern struct curl_slist *headers; +extern char *password; +extern long protocols; +extern const char *proxy; +extern char *proxy_password; +extern const char *proxy_user; +extern bool sslverify; +extern bool tcp_keepalive; +extern bool tcp_nodelay; +extern uint32_t timeout; +extern const char *unix_socket_path; +extern const char *user; +extern const char *user_agent; + +/* The per-connection handle. */ +struct curl_handle { + CURL *c; + bool accept_range; + int64_t exportsize; + char errbuf[CURL_ERROR_SIZE]; +...

...atic struct curl_slist *headers = NULL; > -static char *password = NULL; > -static long protocols = CURLPROTO_ALL; > -static const char *proxy = NULL; > -static char *proxy_password = NULL; > -static const char *proxy_user = NULL; > -static bool sslverify = true; > -static bool tcp_keepalive = false; > -static bool tcp_nodelay = true; > -static uint32_t timeout = 0; > -static const char *unix_socket_path = NULL; > -static const char *user = NULL; > -static const char *user_agent = NULL; > +const char *cainfo = NULL; > +const char *capath = NULL; > +char *cookie...

Hi, I am trying to compile 2.2.3a on an HPUX11 system using HP's native compilers and I am getting the folling errors. cpp: "/usr/include/sys/xti.h", line 488: warning 2001: Redefinition of macro TCP_NODELAY. cpp: "/usr/include/sys/xti.h", line 489: warning 2001: Redefinition of macro TCP_MAXSEG. The above is an example, it happens for each stage of the compile process.

This is an RFC only, at the very least it lacks tests. This implements a rather complex new feature in nbdkit-curl-plugin allowing you to specify an external shell script that can be used to fetch an authorization token for services which requires a token or cookie for access, especially if that token must be renewed periodically. The motivation can be seen in the changes to the docs in patch 2.

Evolution of this patch series: https://www.redhat.com/archives/libguestfs/2020-July/thread.html#00073 Instead of auth-script, this implements header-script and cookie-script. It can be used for similar purposes but the implementation is somewhat saner. Rich.

...ie_script_renew; +extern struct curl_slist *headers; +extern const char *header_script; +extern unsigned header_script_renew; +extern char *password; +extern long protocols; +extern const char *proxy; +extern char *proxy_password; +extern const char *proxy_user; +extern bool sslverify; +extern bool tcp_keepalive; +extern bool tcp_nodelay; +extern uint32_t timeout; +extern const char *unix_socket_path; +extern const char *user; +extern const char *user_agent; + +/* The per-connection handle. */ +struct curl_handle { + CURL *c; + bool accept_range; + int64_t exportsize; + char errbuf[CURL_ERROR_SIZE]; +...

I am having a problem with the number of current processes that I cannot seem to diagnose adequately, and is a possible bug. This will be a bit long, but usually more info is better. I am running dovecot 2.0.16 on a CentOS 5 x86_64 server with the mailstore on gfs (output from dovecot -n at bottom). This is an imap issue. This is mostly to do with one client, but none of my tests indicate an

...c.conf network_interfaces="lo0 em0 dc0 rl0 plip0" kern_securelevel="2" kern_securelevel_enable="YES" linux_enable="YES" named_enable="YES" nisdomainname="NO" sshd_enable="YES" usbd_enable="YES" hostname="sis" tcp_keepalive="YES" tcp_extensions="YES" ifconfig_em0="inet 192.168.128.222/24" ifconfig_dc0="inet 192.168.1.4/24" ifconfig_rl0="inet 10.10.75.126/24" defaultrouter="192.168.128.1" static_routes="net1 net2" route_net1="-net 192.168.0.0/22...

Hi there, Is there some way to configure ipfw to do traffic normalizing ("scrubbing", as in ipf for OpenBSD)? Is there any tool to do it for FreeBSD firewalling? I've heard that ipf was ported on current, anything else? TIA, /Dorin. __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools