Strange "CODE SIGNING" errors in the console.

I get the same here in my logs. I've come to the conclusion that it's normal on a leopard hackintosh.

Though i'm happy to be proved wrong...

I have also wondered this. If there is a way to clean these errors up, that would be nice. Im starting to think it is normal though.

Which release is this? Can you be a little more specific?

I'm running the first Zephyroth 10.5.2 but had that problem since 10.5.1. So I'm kind of used to that, but if there's a way to avoid that message I'll go for it.

eMatoS
"I'm running the first Zephyroth 10.5.2 but had that problem since 10.5.1. So I kind of used to that, but if there's a way to avoid that message I'll go for it."

Same w/ me. There does not appear to be anything wrong w/the workings of the systm. However, if clearing those errors improves performance, i'm for that.

I want to revive this thread and say that I'm plagued by these messages as well. I tried doing a LaunchServices rebuild as suggested at <a href="discussions.apple.com/thread.jspa?threadID=1201327&tstart=60#6080118">this apple discussion thread</a>, as I believe it is related to a "-10810" error, jerking mouse problems, and other performance issues that I and others are having. However, this didn't help the problems. Zeph, if you're listening, what's your take on this one? There are many of us suffering from these issues and others like it. You can see all of our stories, trials, errors, and more here at <a href="osx.kb ot.de/comments.php?DiscussionID=753">this thread</a>.

you can try this
This is a general OS issue, not just an OSx86 (hackintosh) issue. here is your fix:

CODE

sudo nano /System/Library/LaunchDaemons/com.apple.syslogd.plist

after line #23 add two additional strings (these make sure that the syslogd logger only write emergency errors to the system log.

CODE

#23 <string>/usr/sbin/syslogd</string>
#24 <string>-c</string>
#25 <string>0</string>

Optionally you can also cap the log file to a certain file size using:

CODE

#23 <string>/usr/sbin/syslogd</string>
#24 <string>-c</string>
#25 <string>0</string>
#26 <string>-db_max 2500000</string>

this is nice, but will turning off reporting actually do anything performance-wise? it seems the general concern is not necessarily that the messages are showing up, but what is actually causing them to show up in the first place. at one point, i thought little snitch was causing many of these code signing messages to occur, but after many hours of running without it, it seems that they just happen whenever i open/close a program or when OSX performs any sort of automatic maintenance/action. so at this point, i don't think it's anything to worry about, and i'm pretty sure the problems i am having (mouse movement, slowdowns, -10810s) are not related. but who knows? i have yet to find the solution to those things :\

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

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

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

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

I've seen too many of thoes, but in my system it seems fine, no slowdowns or hd activity and the messages still appears even when it's idle.

yes i think everyone is having these error but the question is why are they showing up what is causing them

I used to receive those messages sometime ago, but after updating to the latest kernel from the #10.5 channel on irc.osx86.hu and the latest AppleSMBios from Macdotnub (my.macd otnub.info/content/view/19/26), they have since disappeared. It's definitely worth a shot.

Interesting, because I am also running latest kernel (9.2.0 w/ shutdown fix) and AppleSMBios-27 from macdotnub. Oh, but which AppleSMBios exactly? There are many different ones for different RAM types and Mac identities. I am using the "default" one. Also, what are your specs?

Actually yesterday I upgraded AppleSMBios to the new version from netkas ↗. The previous version I had installed was the hardcoded 667Mhz version. I'm also running the latest 9.2.0 with shutdown fix.

Ah, good to know. Haven't tried that one yet. I'll give it a spin right now.

Running the new AppleSMBIOS right now. Reported RAM speed is wrong of course, but that is always the case for me and Netkas' versions of the file. No biggie. Runs good. Can't say that it did anything for these "code signing" messages, but I think it did cut down on the number of mDNSresponder messages I'm getting, which would be a plus. I could be mistaken though.