{"id":245,"date":"2006-12-30T12:58:18","date_gmt":"2006-12-30T19:58:18","guid":{"rendered":"http:\/\/www.red-sweater.com\/blog\/245\/taming-launchd"},"modified":"2006-12-30T13:13:56","modified_gmt":"2006-12-30T20:13:56","slug":"taming-launchd","status":"publish","type":"post","link":"https:\/\/redsweater.com\/blog\/245\/taming-launchd","title":{"rendered":"Taming Launchd"},"content":{"rendered":"

Developers, and some power users who are reading this have probably heard of launchd<\/a>. It’s Apple’s “mama process,” responsible for launching other processes at startup, login, at regular intervals, or on demand. If you open the Activity Monitor application, and view “All Processes, Hierarchically,” you’ll see that there are only two top-level processes: kernel_task, and launchd. The kernel sits there and does its thing, while launchd spawns all the other processes that make up your Macintosh computing experience.<\/p>\n

\nOne big benefit of launchd to end-users is that most<\/em> of what gets launched can be easily examined by perusing the configuration files. Launchd looks in five well-defined locations for launchable items:\n<\/p>\n

\n\/System\/Library\/LaunchDaemons
\n\/System\/Library\/LaunchAgents
\n\/Library\/LaunchDaemons
\n\/Library\/LaunchAgents
\n~\/Library\/LaunchAgents\n<\/p>\n

\nSo all you have to do to get a feel for (most of) what launchd is up to is start poking around in those directories. For each independent “launch” that launchd controls, you’ll find a corresponding configuration property list file. For instance, you’re guaranteed to find a bunch of examples in \/System\/Library\/LaunchDaemons, and depending on which third-party packages you’ve installed, you might find things in other places, as well.\n<\/p>\n

Launchd In Context: FTP<\/h3>\n

Take a quick look at ftp.plist<\/a>, one of the system launch daemons. Depending on how you’ve configured your system, you’ll either see that a “Disabled” key is present and set to “true,” or it is absent. This corresponds directly to the “FTP Access” item in the System Preference’s “Sharing” panel. Go ahead and toggle the setting in your preferences, and observe that the ftp.plist file is immediately updated to reflect the new setting. This tells launchd that it should no longer consider launching the ftp daemon when an incoming ftp connection is attempted.\n<\/p>\n

\nWhat constitutes an incoming ftp connection? Look further down the ftp.plist and you’ll find an entry with key name “SockServiceName” and a value of “ftp”. Launchd uses this name to lookup the socket port\/protocol information for the named service from \/etc\/services. In this case, when an incoming connection is attempted on port 21, launchd will, if this item is not disabled, launch the daemon at \/usr\/libexec\/ftpd, in order to handle the incoming connection. Groovy, huh? Read more<\/a> about network handlers and other on-demand daemons.\n<\/p>\n

Boot-Time King<\/h3>\n<\/p>\n

\nI said above that these configuration files reveal “most of” what launchd is up to with regard to running things on your system. Because launchd can’t handle all types of configurations, and because its introduction has been sort of gently staged, it’s responsible for running a lot of the older mechanisms like \/etc\/rc, StartupItems, etc. This means that launchd is basically responsible for everything from when the kernel gets loaded on. That includes booting your Mac!\n<\/p>\n

\nThings have been in such flux over the past few years that it’s hard to keep a straight answer when it comes to exactly what takes place at boot time. Excellent overviews such as Mac OS X System Startup<\/a> by Amit Singh, or The Boot Process<\/a> by Apple, are liable to become outdated as launchd continues to evolve.\n<\/p>\n

\nFortunately, the entire process is transparently observable, because launchd is open source<\/a>. If you’re ever in doubt about any nuance of the startup process, just look at the source code<\/a>. The repository even contains the boot-time configuration file “\/etc\/rc”, and the source for antiques like SystemStarter. You can even check out how the boot process is going to look in Leopard<\/a>. (Note: free registration on macosforge.com required). I couldn’t figure out how to check out those repository URLs from the command-line, but I discovered an alternate URL<\/a> that works, and doesn’t seem to require registration.\n<\/p>\n

Editing Launchd Configuration Files<\/h3>\n<\/p>\n

\nIt won’t take you long to discover that the launchd configuration files, while elegant and modular, are a bit of a pain to read, let alone edit. Fortunately, a couple of third-party solutions exist to ease this task.\n<\/p>\n

\nLingon<\/a>, by Peter Borg, is a very powerful editor which also serves as a sort of browser for all the existing configuration files on your Mac. You can selectively start or stop any existing configuration, and it takes care of asking you to authenticate for editing those system-owned files (after warning you profusely not to do so!). It even sports a “wizard” interface that asks in relatively plain English what it is you’re trying to accomplish, and guides you through the creation of new<\/em>, custom launchd configurations.\n<\/p>\n

\nWhile Lingon is essentially easy to use, it has some rough edges which scream for refinement. I’d really like to see the application receive a UI overhaul. Lots of little awkward UI elements and poorly phrased dialog make it slightly less than a 100% success. But it sure beats editing in vi, or even Property List Editor.\n<\/p>\n

\nOne of Lingon’s nicest features is its “Expert” pane, which allows you to examine and edit the raw XML of a configuration at any time. This is so useful that I’d like to see if featured as a full-time view, perhaps in a hideable split view pane. It would be fun to be able to watch the changes live in the XML source while tweaking details in the UI. But Lingon is, in the spirit of launchd itself, open source. So any shortcomings that ultimately get me down can be remedied to my own (or your own) liking.\n<\/p>\n

\nApparently I wasn’t the only person to object slightly to the UI of Lingon. Launchd Editor<\/a> is a $5, closed-source alternative that bites off a much smaller feature set, while trying to improve on the UI of Lingon. It’s clear by observing some of the configuration panes that Launchd Editor was inspired by Lingon (or vice-versa, I’m not positive which came first, but I’d guess Lingon did). Some of the control layout is almost identical to Lingon, but touched up a bit in alignment and wording, mostly for the better.\n<\/p>\n

\nLaunchd Editor is limited by its adoption of a document-centric model, such that the user has to specifically locate and open a configuration file. It also lacks the start\/stop\/load features of Lingon. Overall I’d say it’s worth using Lingon in spite of its rough UI, but minimalists might prefer Launchd Editor.<\/p>\n

Launchd For Developers<\/h3>\n

So far I’ve talked about how the system uses launchd for its services, and sort of alluded to the fact that you might come up with your own configurations to suit your personal needs. But developers should also take heed of launchd as a mechanism for automating tasks on behalf of users. One example of this is Noodlesoft’s Hazel<\/a>, which uses launchd configuration rules to periodically check the status of “watched folders” and perform housekeeping tasks on them. By saving configurations to the user’s LaunchAgents folder, and then loading them with the launchctl<\/a> command-line tool, it pushes off timing responsibility to launchd. Nifty!<\/p>\n

Summary<\/h3>\n

Launchd is a super addition to Mac OS X, and a stellar example of Apple’s commitment to improving Unix for both end-user and architectural benefit. Hopefully if you hadn’t gotten a chance to take a close look at it before, you’ll be encouraged to do so after reading this article.<\/p>\n","protected":false},"excerpt":{"rendered":"

Developers, and some power users who are reading this have probably heard of launchd. It’s Apple’s “mama process,” responsible for launching other processes at startup, login, at regular intervals, or on demand. If you open the Activity Monitor application, and view “All Processes, Hierarchically,” you’ll see that there are only two top-level processes: kernel_task, and […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,21,20,15,23],"tags":[],"class_list":["post-245","post","type-post","status-publish","format-standard","hentry","category-apple","category-darwin","category-hacking","category-programming","category-software-reviews"],"_links":{"self":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts\/245","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/comments?post=245"}],"version-history":[{"count":0,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/posts\/245\/revisions"}],"wp:attachment":[{"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/media?parent=245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/categories?post=245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redsweater.com\/blog\/wp-json\/wp\/v2\/tags?post=245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}