Re: Help tracking down a naughty process

[Tuc]

  
  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
  
I get this from XFree86 and xlock, mostly xlock.

Tuc/TTSG Internet Services, Inc.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Help tracking down a naughty process

[Adam McLaurin]

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.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Help tracking down a naughty process

[Dan Nelson]

In the last episode (Mar 31), Adam McLaurin said:
 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.

Apply this patch:

Index: sys_machdep.c
===
RCS file: /home/ncvs/src/sys/i386/i386/sys_machdep.c,v
retrieving revision 1.91
diff -u -r1.91 sys_machdep.c
--- sys_machdep.c   7 Sep 2003 05:23:28 -   1.91
+++ sys_machdep.c   22 Oct 2003 16:52:49 -
@@ -464,8 +464,8 @@
if (!(uap-start == LDT_AUTO_ALLOC  uap-num == 1)) {
/* complain a for a while if using old methods */
if (ldt_warnings++  NUM_LDT_WARNINGS) {
-   printf(Warning: pid %d used static ldt allocation.\n,
-   td-td_proc-p_pid);
+   printf(Warning: pid %d (%s) used static ldt allocation.\n,
+   td-td_proc-p_pid, td-td_proc-p_comm);
printf(See the i386_set_ldt man page for more info\n);
}
/* verify range of descriptors to modify */

 

-- 
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]