From owner-freebsd-questions@FreeBSD.ORG Wed Mar 31 14:27:46 2004 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 3550C16A4CE for ; Wed, 31 Mar 2004 14:27:46 -0800 (PST) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 150B943D1F for ; Wed, 31 Mar 2004 14:27:46 -0800 (PST) (envelope-from adam.mclaurin@gmx.net) Received: from 146-115-126-186.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com ([146.115.126.186] helo=jake) by smtp02.mrf.mail.rcn.net with smtp (Exim 3.35 #4) id 1B8oBU-0007Vd-00 for questions@freebsd.org; Wed, 31 Mar 2004 17:27:44 -0500 Date: Wed, 31 Mar 2004 17:27:40 -0500 From: Adam McLaurin To: questions@freebsd.org Message-Id: <20040331172740.1408dd2b.adam.mclaurin@gmx.net> Organization: X-Mailer: Sylpheed version 0.9.9-gtk2-20040229 (GTK+ 2.2.4; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Help tracking down a naughty process 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, 31 Mar 2004 22:27:46 -0000 Since upgrading to 5.2.1-p4-RELEASE last night, I have seen the following warnings a few times in my /var/log/messages: Mar 31 16:49:14 jake kernel: Warning: pid 37735 used static ldt allocation. Mar 31 16:49:14 jake kernel: See the i386_set_ldt man page for more info Trouble is, by the time I go to check what pid 37735 is, it's already terminated without a trace. Now the i386_set_ldt man page warns strongly against it's usage, so I'd like to catch this bugger before it causes any problems, but I don't really know how, since it seems to be something that only runs for a couple seconds and then exits (could be part of some script somewhere, I don't know). When I upgraded, I did do a nice 'portupgrade -raRf' to recompile everything, and almost everything recompiled without problems (although it took nearly 36 hours to do it). I can't imagine what might be doing this, although I am suspicious of wine (just b/c it often does naughty things). Any suggestions on catching this process in action? Thanks. -- Adam "satyam, shivam, sundaram" P.S. Please CC your reply to me, since I am no longer subscribed to this list. Thanks.