NAME
DirectoryService — DirectoryService daemon (a part of Mac OS X’s Open
Directory architecture)
SYNOPSIS
DirectoryService [-hv]
DESCRIPTION
Apple’s Open Directory architecture includes source code for both direc-
tory client access and directory servers. Open Directory forms the foun-
dation of how Mac OS X accesses all authoritative configuration informa-
tion (users, groups, mounts, managed desktop data, etc.). Mac OS X
obtains this information via abstraction APIs, enabling use of virtually
any directory system. Configuration of Open Directory is done through
the Directory Access applications in /Applications/Utilities. This
application can configure plugin settings, including turning on/off vari-
ous directory services.
Open Directory Access
Directory Services is a core part of the Open Directory technology.
Directory Services provides a client read/write/authentication API
abstraction for accessing directory-based data. Directory Services con-
sists of an access API, and an API daemon, and a plug-in API.
An additional element of Open Directory is the existing Darwin component
of lookupd that provides a read-only abstraction for accessing all BSD
configuration information. Both lookupd and Directory Services work in
conjunction with each other via the DSAgent to provide authoritative and
consistent configuration information to all processes running on Mac OS X
regardless of which Directory API they are using. The source code for
DSAgent is also available.
More information can be accessed from the Darwin Open Directory Page:
http://developer.apple.com/darwin/projects/opendirectory/
Open Directory Servers
Apple’s Open Directory Servers are OpenLDAP and NetInfo. OpenLDAP and
NetInfo are included as part of Mac OS X Desktop and Server, and are also
included with Darwin. Both OpenLDAP and NetInfo provide a robust and
scalable platform for serving directory based configuration information
for both stand-alone and networked CPUs. OpenLDAP and NetInfo share the
same datastore and both separately consist of:
o Access API
o Server process
o Command line tools for displaying and modifying the contents of the Directory Server data.
Documentation
Directory Services Access API and Plug-in API is documented at:
http://developer.apple.com/techpubs/macosx/Networking/
The headers for the DirectoryService APIs can also be found in the fol-
lowing location:
/System/Library/Frameworks/DirectoryService.framework/Headers/
OPTIONS
The options are as follows:
-h Display list of options
-v Display the release version.
PLUGINS
The following plugins can be managed using the Directory Access applica-
tion.
o BSD (Flat File and NIS)
o NetInfo
o LDAPv3
o Search
o SMB
o SLP
o Bonjour (zero-conf)
o Appletalk
o PasswordServer
DIAGNOSTICS
There are two helpful signals you can send to the DirectoryService daemon
to help diagnose problems you may be having. (Example: % sudo killall
-USR1 DirectoryService). USR2 logging automatically turns off after 5
minutes.
o USR1 Turns Debug Logging (on/off) See /Library/Logs/DirectoryService/DirectoryService.debug.log
o USR2 Turns API Logging (on/off) See /var/log/system.log
NAME
crashreporterd — crash detection and panic logging daemon
SYNOPSIS
crashreporterd
DESCRIPTION
crashreporterd is the daemon responsible for detecting application
crashes. crashreporterd listens for mach exceptions and when it detects
a mach exception launches crashdump to investigate the crash and report
it to the user.
crashreporterd is also responsible for writing panic information to
/Library/Logs/panic.log when the system is rebooted after a panic.
crashreporterd should only be started at boot time by the CrashReporter
startup item - killing or restarting crashreporterd at any other time
will lead to upredictable behavior when an application crashes. Adminis-
trators can edit the CRASHREPORTER entry in /etc/hostconfig to prevent
crashreporterd from starting at boot time.
FILES
/usr/libexec/crashreporterd daemon
/System/Library/StartupItems/CrashReporter/ startup item
/etc/hostconfig configuration
/Library/Logs/panic.log panic log
Next One ![]()
Pages: 1 2 3
Comments Off