From owner-freebsd-questions@FreeBSD.ORG Mon Aug 7 08:32:46 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2731616A50D for ; Mon, 7 Aug 2006 08:32:46 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38DB343E1D for ; Mon, 7 Aug 2006 08:31:33 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1GA0Uy-0009qO-MC for freebsd-questions@freebsd.org; Mon, 07 Aug 2006 12:30:08 +0400 Received: from localhost.stc ([127.0.0.1] helo=sysadm.stc) by sysadm.stc with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GA0Vb-0007X4-8r for freebsd-questions@freebsd.org; Mon, 07 Aug 2006 12:30:47 +0400 Received: (from igorr@localhost) by sysadm.stc (8.13.6/8.13.6/Submit) id k778Uldh028957 for freebsd-questions@freebsd.org; Mon, 7 Aug 2006 12:30:47 +0400 (MSD) (envelope-from igorr) Date: Mon, 7 Aug 2006 12:30:47 +0400 From: Igor Robul To: freebsd-questions@freebsd.org Message-ID: <20060807083047.GB27084@sysadm.stc> References: <20060801150226.0c911297.wmoran@collaborativefusion.com> <000401c6b59e$92d942d0$3c01a8c0@coolf89ea26645> <20060801152107.eba203fa.wmoran@collaborativefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060801152107.eba203fa.wmoran@collaborativefusion.com> User-Agent: Mutt/1.5.11 X-Archived: Yes Subject: Re: Reducing the timeout on a TCP connection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2006 08:32:46 -0000 On Tue, Aug 01, 2006 at 03:21:07PM -0400, Bill Moran wrote: > In response to "Ted Mittelstaedt" : > > > This is why the snmp protocol uses UDP, Bill. > > > > You need to use something other than TCP for > > monitoring. > > Well ... if I'm monitoring a server that uses TCP (PostgreSQL) I can't > rightly establish whether or not it's successfully accepting connections > unless I used TCP as well. > > I understand where you're coming from, but I can't see how I can use > UDP to solve my problem. You can do 2-step monitoring: 1) Monitor1 monitors PostgreSQL via Unix domain socket, possible also it monitors presense of postmaster process 2) Monitor2 monitors Monitor1 and you "connect" to Monitor2 via UDP.