Does anyone recognize what got turned on/installed on one of my boxes?

Linux version 2.4.20-itanium-smp (root@pique) (gcc version 3.2.3 (Debian)) #1 SMP Tue Jun 10 13:56:24 MDT 2003

I have several Itanium2/Debian boxes, and just one of them is tracing all my process invocations in /var/log, the traces show up in three files simultaneously, /var/log/kern.log, messages, and syslog.

They all look like this:

Sep 7 09:50:46 rx2600-01 kernel: rm(2353): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: rm(2355): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: rm(2356): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: rm(2357): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: rm(2358): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: rm(2359): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: find(2354): <sc1236(0,2000000000240200,0,2000000000275df8)>
Sep 7 09:50:46 rx2600-01 kernel: rm(2360): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: dh_clean(2349): <sc1236(0,2000000000610200,0,2000000000645df8)>
Sep 7 09:50:46 rx2600-01 kernel: rules(2339): <sc1236(0,2000000000270200,0,20000000002a5df8)>
Sep 7 09:50:46 rx2600-01 kernel: tail(2363): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: debian(2362): <sc1236(0,2000000000610200,0,2000000000645df8)>
Sep 7 09:50:46 rx2600-01 kernel: tar(2365): <sc1254(0,6000000000011390,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: tar(2365): <sc1236(0,2000000000270200,0,20000000002a5df8)>
Sep 7 09:50:46 rx2600-01 kernel: gzip(2364): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: md5sum(2367): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: sh(2366): <sc1236(0,20000000002f0200,0,2000000000325df8)>
Sep 7 09:50:46 rx2600-01 kernel: dpkg-source(2361): <sc1236(0,2000000000610200,0,2000000000645df8)>
Sep 7 09:50:46 rx2600-01 kernel: rules(2368): <sc1254(0,60000fffffffa100,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: dh_testdir(2369): <sc1236(0,0,3,0)>
Sep 7 09:50:46 rx2600-01 kernel: make(2370): <sc1254(0,60000fffffffa0e0,3,0)>
...
...

..everything!

I don't know what happened to that one box, does anyone recognize the format?

Could be 2 things (to my knwoledge):

1) A debugging flag is set somewhere,

2) Read somewhere that this could be a kernel bug, upgrading to a more recent kernel should fix this.

Hope this points you in the right direction.

Well that looks like you are compiling something from source so have you done some compiling recently? Also the only hit a Google Linux search seems to get leads to this http://www.gelato.unsw.edu.au/linux-...407/10263.html thread on a bug in an ia64 system.