they say it will
because your system spends less time reporting errors so it frees the system up

hell, it's worth a try. i'll let you know how it goes. it'll take a while though, because i need to have the system up for many hours before i know whether the problem will recur or not. thank you very much for this info. wish me (and all of us) luck

good luck

Mar 20 03:35:03 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=836[lssave] clearing CS_VALID
Mar 20 03:36:01 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=840[Console] clearing CS_VALID
Mar 20 03:36:01 bill-hasts-macpro31 fseventsd[43]: scan_old: bailing out because device mounted @ /Volumes/Untitled has dls 0x0 and dls->fci 0x0


im still getting them too

after modifying syslogd?

yeah still getting those errors

me too

guess that didn't work
i wish someone could explain this error

Here's another one:

kernel CODE SIGNING: cs_invalid_page: p=268[mdworker] clearing CS_VALID

---

 Snow Leopard 10.6.7  Gigabyte GA-P35-DS3P  Intel Q6600 @ 3Ghz  Corsair CM2X2048-6400DHX  Gigabyte HD5770 Silent Cell  Samsung SyncMaster 2494SW  ALC889a  Creative T5400 5.1  Maxtor 380215AS  Pioneer DVR-215D  Presonus Inspire 1394  KRK Rokit 5  Wacom Bamboo One 
 SL USB Guide => http://www.infinitemac.com/f57/guide...k-drive-t3705/ 

here is a few more
Mar 20 05:25:24 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=710[Console] clearing CS_VALID
Mar 20 05:25:44 bill-hasts-macpro31 Finder[413]: NSOpenGLAutoscaleBounds=NO
Mar 20 05:30:18 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=716[mdworker] clearing CS_VALID
Mar 20 05:32:56 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=722[lssave] clearing CS_VALID
Mar 20 05:33:02 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=723[Console] clearing CS_VALID
Mar 20 05:34:11 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=726[lssave] clearing CS_VALID
Mar 20 05:38:56 bill-hasts-macpro31 mDNSResponder[38]: mDNSPlatformRawTime: last_mach_absolute_time A7579E16000003DF
Mar 20 05:38:56 bill-hasts-macpro31 mDNSResponder[38]: mDNSPlatformRawTime: this_mach_absolute_time A7573680000003DF
Mar 20 05:38:58 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=728[lssave] clearing CS_VALID
Mar 20 05:46:17 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=733[mdworker] clearing CS_VALID
Mar 20 05:46:18 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=735[lssave] clearing CS_VALID
Mar 20 06:03:26 bill-hasts-macpro31 mDNSResponder[38]: mDNSPlatformRawTime: last_mach_absolute_time EB3FFD3900000535
Mar 20 06:03:26 bill-hasts-macpro31 mDNSResponder[38]: mDNSPlatformRawTime: this_mach_absolute_time EB3E5EF600000535
Mar 20 06:03:28 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=742[lssave] clearing CS_VALID
Mar 20 06:03:28 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=743[mdworker] clearing CS_VALID
Mar 20 06:10:52 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=746[Console] clearing CS_VALID
Mar 20 06:10:54 bill-hasts-macpro31 kernel[0]: CODE SIGNING: cs_invalid_page: p=748[lssave] clearing CS_VALID

guess these are emergency errors