From owner-freebsd-questions Tue Nov 30 7:56:18 1999 Delivered-To: freebsd-questions@freebsd.org Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id 2992115A08 for ; Tue, 30 Nov 1999 07:55:37 -0800 (PST) (envelope-from per@erix.ericsson.se) Received: from super.du.uab.ericsson.se (per@super.du.uab.ericsson.se [134.138.176.16]) by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id QAA00488; Tue, 30 Nov 1999 16:55:31 +0100 (MET) Received: (from per@localhost) by super.du.uab.ericsson.se (8.9.3/8.9.3/erix-1.7) id QAA05356; Tue, 30 Nov 1999 16:55:30 +0100 (MET) Date: Tue, 30 Nov 1999 16:55:30 +0100 (MET) From: Per Hedeland Message-Id: <199911301555.QAA05356@super.du.uab.ericsson.se> To: dante-misc@inet.no, scrappy@hub.org Subject: Re: iotimeout value in sockd.conf ... Cc: anders@fix.no, freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: >A quick grep of the log file shows that sockd, at least, feels that the >timeout is there: > >grep timeout /home/log/sockd.log >Nov 24 09:24:02 demeter sockd[96274]: negotiate timeout: 30s >Nov 24 09:24:02 demeter sockd[96274]: I/O timeout: 3600s >But it doesn't look like sockd (under FreeBSD) is honoring it... > >'anders@fix.no' just created a FreeBSD port of this, so I'm CC'ng him in >on this email, to see if if can back me up, or if this is specific to just >me. I've also CC'd freebsd-questions on this, in the hopes that there are >*at least* a few FreeBSD users out there using Dante and who can check >their setups... The I/O timeout works perfectly for me on FreeBSD 3.2-RELEASE (I frequently get my own idle sessions diconnected by it:-). >If someone wants to give me some sort of direction on how to go about >using gdb to debug this particular problem, I'm open to suggestions, I can >do really simple things on core files with gdb, but that is about it at >this time... Sorry, don't have any suggestions for that - I suppose you've verified that these long-running processes aren't leftovers from an earlier sockd invocation that didn't have iotimeout set? >Okay, I'm very confused, but what is the point of io_gettimeout()? >First, instead of just setting 'timeout' and passing that to select()? >Don't I want the select() to "wait" iotimeout seconds from when it was >called? One process handles multiple connections, it has to notice one of them being idle even if the others have traffic (i.e. they cause select() to return before the timeout). --Per Hedeland per@erix.ericsson.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message