From owner-freebsd-questions@FreeBSD.ORG Wed Oct 29 11:08:10 2003 Return-Path: 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 AC91016A4CE for ; Wed, 29 Oct 2003 11:08:10 -0800 (PST) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B82F943FBD for ; Wed, 29 Oct 2003 11:08:09 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.12.10/8.12.9) with ESMTP id h9TJ87F1001495; Wed, 29 Oct 2003 14:08:07 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <002101c39e22$8fe2ada0$04fea8c0@moe> References: <002101c39e22$8fe2ada0$04fea8c0@moe> Date: Wed, 29 Oct 2003 14:08:06 -0500 To: "Charles Howse" , From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Smbd process not disconnecting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2003 19:08:10 -0000 At 7:42 AM -0600 10/29/03, Charles Howse wrote: > >Note below, that the connection was opened on the 28th, but >did not close, however the connection to "Seeds" closed >about 4 mins after I opened it. > >Snippet from /var/log/moe.log >[2003/10/28 12:11:13, 1] smbd/service.c:make_connection_snum(698) > moe (192.168.254.4) connect to service WWW initially as user nobody >(uid=65534, gid=65534) (pid 3064) >[2003/10/28 15:31:04, 1] smbd/service.c:make_connection_snum(698) > moe (192.168.254.4) connect to service Seeds initially as user nobody >(uid=65534, gid=65534) (pid 3064) >[2003/10/28 15:35:49, 1] smbd/service.c:close_cnum(880) > moe (192.168.254.4) closed connection to service Seeds > >Am I way off target here, or do I have a process that isn't >disconnecting when it should? > >How can I find out why the connection to "WWW" didn't close, >and prevent that from happening in the future? I believe that what happens is that samba starts a process which handles connections as they come-and-go from the client machine. If you make additional connections, you'll notice that they all happen to 'pid 3064' (in the above example). I expect samba does this because there are times when the windows client will make a whole bunch of very short-lived connections, and it's better to have one process which keeps track of client-information than to rebuild all that information every time. I'm not much of an expert on the low-level details, but I can say that what you're seeing is also what I've seen, and that I believe samba is supposed to work that way. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu