![]() I was just getting ready to type "128 MB and three hours, but before I had a chance it was up to four hours. In the meantime, Console indicates several hundred mdworker.shared -> SGKILL instances, as many as five per second. As I write this, T2M2 the progress is up to 128 Mb with a backup rate of 0.15 Mb/sec, and now the time remaining shows 2 hours instead of 1 hour. According to T2M2 it backs up 50, 60 Mb or so, and then stalls for 10-15 minutes.Īt this moment it is showing 84.0 Mb of 1.6 GB, with an estimated time of 1 hour remaining.Īt times it will show backup speeds up to 6 MB/s, suggesting the network is OK, at least up to these speeds. It then reports, say, 2.3 GB to be backed up and starts the process. I realize wi-fi/NAS will be slow, but the problem(s) clearly appear to be with TM itself and/or Spotlight.ĭespite minimal activity on Mac, TM requires 10-15 minutes (or more) of preparation. TM is running alternatively over wifi on two rather old WD MyBookLive NAS drives that appear to be fully functional. There will be periods of quiet, and turning off Time Machine seems to help. I have T2M2 from EclecticLight, along with other EL utilities, and I have read most of his (very useful) blogs.īelow is a typical snapshot from Console. I have downloaded both etrecheckPro and Malwarebytes. With all due respect, that answer is terse to the point of being useless.Ĭonsole help does not say anything about it. The spindump references indicate something is crashing." The sum total of the answer says, "It is posting log information so developers can update their apps. The link provided above was from 2015, and was tagged with 79 other people indicating they had the same problem. I have been searching high and low for some background information or general explanation of for days, with no luck. I don't want to appear ungrateful, or obnoxious, but this is really frustrating. ![]() They can't conceive of that being normal, of that happening on a billion Apple devices all over the world, all day long, every day, without ever ending. But instead of a cool animation displayed in a film for 10 seconds, it scrolls on and on, for minute, hours, days, without ever once stopping. It can be like the scrolling text in the matrix. I have seen more than one person completely lose touch with reality when looking at the Console. These days, I get very suspicious when I see people reference the Console app. Apple took a useful tool and architecture and effectively destroyed it. It can easily log hundreds of messages a second. Then, since there was no performance impact from logging messages, every Apple app on the system (and there are hundreds) started logging information at a mind-bogglingly low level of minutiae. Some "clever" folks at Apple thought it would be nice to redesign the system logging architecture so it could handle an infinite amount of debugging messages. In theory, it is designed for programmers to analyze log messages. Plus, the messages it prints have little to no value to anyone. I don't recommend running Console at all. Below is a typical snapshot from Console. it will not affect the parent process, at least in theory. If that task fails, or has a security issue, or locks up, etc. Launchd works together with XPC to allow an app to break off a piece of itself to perform some specific task. The "d" stands for "daemon", which is a low-level system process that is always running in the background to handle low-level tasks. The launchd architecture itself is simply a system for "launch"-ing processes. It doesn't have anything in particular to do with launchd other than being a low-level interface that works closely with launchd. It is fairly resource-intensive so 3rd party developers can use it on macOS, but not iOS. It is a general feature available to any macOS app and used throughout Apple's iOS and macOS operating systems. The whole idea behind it is that it is an easy to use API (Application Programming Interface) that doesn't require the programmer to know the low-level details of the syntax. Here is an old Apple WWDC developer video describing it back in the day: It describes one process (an app, more or less) communicating with another one. Funny how these things get lost over the years. Of course, Apple doesn't even use the "X" anymore. I've never even thought about it either.Īpparently, it is "IPC" for "MacOS X", therefore "X-IPC" or just "XPC". I don't think anyone has ever asked it before. For example, what does 'xpc' mean? What is the syntax? Where does it come from? Does it only work with 'launchd', or is it a more general feature?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |