4 Replies Latest reply: Nov 2, 2008 8:26 AM by Michael Conniff
imcleod Level 1 Level 1 (0 points)
Does anyone know the root of and the fix for the following messages I am receiving from console?

11/2/08 7:10:21 AM com.apple.coreservicesd[63] NOTE: Using non-mach-based version of client -> server communication, via direct function calls.

11/2/08 7:10:28 AM mdworker[11640] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.

Any input would be great.
Thank you,
Ian

MacBook Pro, Mac OS X (10.5.5)
  • 1. Re: Repeating console messages
    Barry Hemphill Level 7 Level 7 (34,510 points)
    Hello Ian:

    IMHO, unless you are having problems, reading console logs is a waste of time. Many of the messages are "informational" but, from a practical standpoint, useless to a user.

    Barry
  • 2. Re: Repeating console messages
    Michael Conniff Level 7 Level 7 (33,120 points)
    How was Leopard installed on your machine? Did it come with the machine, or did you update from Tiger? If so, how? An Upgrade, or an Erase & Instal?

    I ask because messages like your second one were very common in Tiger and before (and were no big deal) but I don't recall seeing them in Leopard, so I'm just wondering if your installation was different in some way.

    I haven't seen your first message anywhere; but note that it says "NOTE", rather than "Warning" or "Error".

    Even if we could establish the origin of the messages, there is unlikely to be a fix other than some future Software Update.
  • 3. Re: Repeating console messages
    imcleod Level 1 Level 1 (0 points)
    Hi Michael,
    My installation was factory installed on a refurbished machine. I used Migration Assistant to bring my data from a PB G4 running 10.4.11.

    Thank you,
    Ian
  • 4. Re: Repeating console messages
    Michael Conniff Level 7 Level 7 (33,120 points)
    imcleod wrote:
    My installation was factory installed on a refurbished machine. I used Migration Assistant to bring my data from a PB G4 running 10.4.11.

    OK, it is possible you brought over a bad (funny?) plist with you. If you are still concerned, you can do a quick check using Terminal:

    Open the Terminal (from /Applications/Utilities) and copy and paste the following into the Terminal window followed by a return:
    plutil -lint *.plist | grep -v OK

    Any .plist file it doesn't like will be listed: if it just comes straight back to the prompt, like mine does, it can't find any problem.

    If you do find a problem, post and let us know.