Understanding Notation Conventions
The following conventions are used throughout this book.

Summary

Notation
monospaced font $ [text_in_brackets] (one|other)
Indicates A command or other text typed in a Terminal window A shell prompt An optional parameter Alternative parameters (use one or the other) A parameter you must replace with a value A parameter that can be repeated A displayed value that depends on your server configuration

italicized

[.] <angle brackets>
Commands and Other Terminal Text
Commands or command parameters that you enter, along with other text that appears in a Terminal window, are shown in this font. For example: You can use the doit command to get things done. When a command is shown on a line by itself in this manual, it is preceded by a dollar sign and a space that represent the shell prompt. For example:

$ doit

To use this command, enter it without the dollar sign and the space in a Terminal window, and then press Return. (Terminal is found in /Applications/Utilities/.)
Command Parameters and Options
Most commands require parameters to specify command options or the item to which the command is applied to.

Preface About This Guide

Parameters You Must Enter as Shown If you must enter a parameter as shown, it appears following the command in the same font. For example:

$ doit -w later -t 12:30

To use the command in this example, enter the entire line as shown (without the $ and space). Parameter Values You Provide If you must provide a value, its placeholder is italicized and has a name that indicates what you need to provide. For example:

$ doit -w later -t hh:mm

In this example, you replace hh with the hour and mm with the minute, as shown in the previous example. Optional Parameters If a parameter is not required, it appears in square brackets. For example:

$ doit [-w later]

To use the command in this example, enter doit or doit vary, but you perform the command either way.

-w later. The

result might
Alternative Parameters If you must enter one of a number of parameters, theyre separated by a vertical line and grouped within parentheses (|). For example:

$ doit -w (now|later)

To perform this command, enter doit

-w now

or doit

-w later.

Default Settings
Descriptions of server settings usually include the default value for each setting. When this default value depends on your configuration (such as the name or IP address of your server), its enclosed in angle brackets. For example, the default value for the IMAP mail server is the host name of your server. This is indicated by mail:imap:servername = "<hostname>."
Commands Requiring Root Privileges

Terminal presents a prompt when it is ready to accept a command. The prompt you see depends on your Terminal and shell preferences, but it often includes the name of the host youre logged in to, your current working folder, your user name, and a prompt symbol. For example, if youre using the default bash shell, the prompt appears as:

server1:~ anne$

where you are logged in to a computer named server1 as the user named anne, and your current folder is annes home folder (~). Throughout this manual, where a command is shown, the prompt is abbreviated as $.
Specifying Files and Folders
Most commands operate on files and folders, the locations of which are identified by paths. The folder names that make up a path are separated by slash characters. For example, the path to the Terminal application is /Applications/Utilities/Terminal.app. Standard shortcuts used to represent specific folders are shown in the following table. Because they are relative to the current folder, these shortcuts eliminate the need to enter full paths in many situations.

Path string

Description A single period represents the current folder. This value is often used as a shortcut to eliminate the need to enter in a full path. For example, the string./Test.c represents the Test.c file in the current folder. Two periods represent the parent folder of the current folder. This string is used for navigating up one level from the current folder through the folder hierarchy. For example, the string./Test represents a sibling folder (named Test) of the current folder. The tilde character represents the home folder of the user logged in. In Mac OS X, this folder resides in the local /Users folder or on a network server. For example, to specify the Documents folder of the current user, you would specify ~/Documents.
File and folder names traditionally include letters, numbers, a period, or the underscore character. Avoid most other characters, including space characters. Although some Mac OS X file systems permit the use of these other characters, including spaces, you might need to add single or double quotation marks around pathnames that contain them. For individual characters, you can also escape the characterthat is, put a backslash character immediately before the character in your string. For example, the pathname My Disk is My Disk or My\ Disk.

$ PATH=/bin:/sbin:/user/bin:/user/sbin:/system/Library/ export PATH
This modifies the environment variable PATH with the value assigned. To view all environment variables, enter the following:
When you launch an application from a shell, the application inherits much of the shells environment, including exported environment variables. This form of inheritance can be a useful way to configure the application dynamically. For example, your application can verify for the presence (or value) of an environment variable and change its behavior accordingly. Different shells support different semantics for exporting environment variables, so see the man page for your preferred shell for further information. Although child processes of a shell inherit the environment of that shell, shells are separate execution contexts that do not share environment information with one another. Thus, variables you set in one Terminal window are not set in other Terminal windows. After you close a Terminal window, variables you set in that window are gone. If you want the value of a variable to persist between sessions and in all Terminal windows, you must set it in a shell startup script. Another way to set environment variables in Mac OS X is with a special property list in your home folder. At login, the computer looks for the ~/.MacOSX/environment.plist file. If the file is present, the computer registers the environment variables in the property list file.
Executing Commands and Running Tools
To execute a command in the shell, enter the complete pathname of the tools executable file, followed by arguments, and then press Return. If a command is located in one of the shells known folders, you can omit path information and enter the command name. The list of known folders is stored in the shells PATH environment variable and includes the folders containing most command-line tools. For example, to run the ls command in the current users home folder, you could enter the following at the command line and press Return:

host:~ anne$ ls

To run a command in the current users home folder, you would precede it with the folder specifier. For example, to run MyCommandLineProg, you would use something like the following:
host:~ anne$./MyCommandLineProg
To launch a tool package, you can use the open command (open MyProg.app) or launch the tool by entering the pathname of the executable file inside the package, usually something like./MyProg.app/Contents/MacOS/MyProg. When entering commands, if you get the message command spelling. Here is an example:
server:/ anne$ sudo serversetup -getHostname serversetup: Command not found. not found, check
If the error recurs, the command youre trying to run might not be in your default search path. You can add the path before the command name, for example:

Mac OS X Server v10.5 supports the following commands: nvram, tdm, and other.
none, pxe, disk, diag, cdrom,
For example, entering the following command and then restarting an Xserve system starts the system in Target Disk Mode:
$ ipmitool chassis bootdev tdm
After the system starts, the ipmitool command reverts to the default setting (none). Restarting the Xserve system without running the ipmitool command does not change the boot device order. For more information about ipmitool, see its man page.
Installing Server Software and Finishing Basic Setup
Use this chapter to learn the commands to install, set up, and update Mac OS X Server software on local or remote computers.
This chapter explains the commands to perform software setup and installation tasks. Some computers come with Mac OS X Server software installed. However, you might want to upgrade from a previous version, change a computer configuration, automate software installation, or refresh your server environment.
Installing Server Software
To install Mac OS X Server or other software on a computer, use the /usr/sbin/installer tool. You can use the installer tool locally or remotely. The installer tool requires at least two arguments: the installation package and the destination of the installation package. For a standard installation, your target would be the root drive. Here is an example installation command:
$ installer -pkg OSInstall.mpkg -target /
Other useful options include: langThe operating system package requires that you choose a language. This flag allows you to do so from the command line. The argument is a two-character ISO language code. For English, its en. verbosePrints the details of the installation. Its useful for monitoring progress. For more information, see the installer man page.
To use the installer to install Mac OS X Server software: 1 Start the target computer from the first installation CD or the installation DVD. The procedure you use depends on the target computer hardware: If the target computer has a keyboard and an optical drive, insert the first installation disc into the optical drive; then hold down the C key on the keyboard while restarting the computer. If the target computer is an Xserve with a built-in optical drive, start the computer using the first installation disc by following the instructions for starting from a system disc in the Xserve Users Guide. If the target computer is an Xserve with no built-in optical drive, you can start it in target disk mode and insert the installation disc into the optical drive on your administrator computer. You can also use an external FireWire optical drive or an optical drive from another Xserve system to start the computer from the installation disc. Instructions for using target disk mode and external optical drives are in the Quick Start guide or Xserve Users Guide that came with your Xserve system. 2 If youre installing on a local computer, when Installer opens choose Utilities > Open Terminal to open the Terminal application. If youre installing on a remote computer, from Terminal on an administrator computer or from a UNIX workstation, establish an SSH session as the root user with the target computer, substituting ip_address with the target computers actual IP address:

Viewing or Changing Apple Event Response
To see if the system is set to respond to remote events:
$ sudo systemsetup -getremoteappleevents
To set the server to respond to remote events:
$ sudo systemsetup -setremoteappleevents (on|off)
Creating the Groups Share Point
To create the Groups share point:
$ serversetup -createGroupsSharePoint
Viewing or Changing Language and Keyboard Settings
To view or change language settings, use the serversetup tool (or the International pane of System Preferences). To view the primary language:
$ serversetup -getPrimaryLanguage
To view the installed language:
$ serversetup -getInstallLanguage
To set the installation language:
$ sudo serversetup -setInstallLanguage language

To select a keyboard:

$ sudo serversetup -setKeyboardSelection ScripID(0) kbResID(0) ResName(U.S.)
$ sudo serversetup --setNewPrimaryLanguage adminshortname primaryLanguage installLanguage
To view the script setting:
$ serversetup -getPrimaryScriptCode
Viewing and Changing Login Settings
You can enable or disable the Restart and Shutdown buttons that appear in the login dialog. To disable or enable the Restart and Shutdown buttons in the login dialog:
$ sudo serversetup -setDisableRestartShutdown (0|1) 0
disables the buttons and 1 enables the buttons.
To view the current setting:
$ serversetup -getDisableRestartShutdown
Setting Network Preferences
Use this chapter to learn the commands to change network settings on a server.
Mac OS X Server provides command-line control to manage servers in a mixedplatform environment and to configure, deploy, and manage powerful network services. These tools make it easy to configure and maintain core network services, while providing the advanced features and functionality required by experienced IT professionals.
Configuring Network Interfaces
To configure network interfaces, Mac OS X Server provides networksetup and serversetup. Although ifconfig (the standard UNIX tool for configuring networks) is available, its better to use networksetup and serversetup because if you use ifconfig, your computer will be out of sync and will revert to using the contents of preferences.plist after a restart. You can still use ifconfig to view the network interface configuration. This is particularly beneficial when your computer is using an autonegotiated Ethernet connection. For more information, see the networksetup and serversetup man pages.
Managing Network Interface Information
This section describes commands you address to a specific hardware device (for example, en0) or port (for example, Built-in Ethernet). If you prefer to work with network port configurations following the approach used in the Network preferences pane of System Preferences, see the commands in Managing Network Port Configurations on page 67.

Changing Configuration Precedence
To list the configuration order:
$ sudo networksetup -listnetworkserviceorder
The configurations are listed in the order that theyre tried when a network connection is established. An asterisk (*) marks an inactive configuration. To change the order of port configurations:
$ sudo networksetup -ordernetworkservices config1 config2 [config3] [.]

Managing TCP/IP Settings

TCP/IP is a set of layered protocols that allow communication between computers on a high-speed network. You can use the following commands to change the TCP/IP settings of a server.
Changing a Servers IP Address
The servers setup must reflect the network settings of the servers primary interface. The primary interface is the topmost active connection in the Network pane of System Preferences. When using your server as a gateway to the Internet, the server uses the primary interface to connect to the Internet. Therefore, during server setup, you configure the primary interface to use the servers public IP address and DNS information. The server setup program uses this information to configure other server components (such as Open Directory, Kerberos, and Password Server). As such, the IP address and the DNS settings of the primary interface and these other components must always match. If at some point you change the IP address or DNS name of the primary interface, the system will run the changeip command within a minute or two. If not, you must register the IP address change with the server setup program. The changeip command makes all necessary changes at once, updating the settings of all components configured during server setup, including Open Directory, Kerberos, and Password Server. The changeip command is a python script that runs tools from the /usr/libexec/ changeip folder. Three tools are available: changeip_ds, changeip_jabber, and changeip_mail. The changeip_ds tool updates the following local configuration files: /Library/Preferences/DirectoryService/DSLDAPv3PlugInConfig.plist /etc/openldap/slapd_macosxserver.conf /etc/hostconfig (if there is a static hostname) /etc/smb.conf The changeip_ds tool also updates the following records in the local directory domain, as well as a parent directory domain, if specified: AuthAuthority and HomeDirectory in user records Addresses and hostname in machine records Addresses and hostname in computer records Mount paths and addresses in mount records Addresses in LDAP and Password Server config records The changeip_jabber tool updates the jabber configuration using serveradmin. The changeip_mail tool updates the mailman, postfix, and imap configurations using serveradmin.

$ ifconfig bond_interface_name bondev physical_interface
The bond_interface_name parameter is the name of the pseudo device and the physical_interface parameter is the Ethernet interface you want to associate with the pseudo device (for example, en0). If this is the first physical interface to be associated with the bond interface, the bond interface inherits the Ethernet address from the physical interface. Physical interfaces that are added to the bond interface have their Ethernet address reprogrammed so members of the bond have the same Ethernet address. If the physical interface is subsequently removed from the bond, a new Ethernet address is chosen from the remaining interfaces, and interfaces are reprogrammed with the new Ethernet address. If no remaining interfaces exist, the bond interfaces Ethernet address is cleared.
To remove an Ethernet interface from a bond virtual device (pseudo device):
$ ifconfig bond_interface_name -bondev physical_interface
The link status of the bond interface depends on the state of link aggregation. If no active partner is detected, the link status remains inactive. To monitor the IEEE 802.3ad Link Aggregation state, use the -b option. For more information, see the ifconfig man page. Configuring Ethernet Link Aggregation You can also use networksetup to configure Ethernet Link Aggregation. The following commands are supported. To see if a device can be added to a bond:
$ sudo networksetup -isBondSupported device
To create a bond and add devices to it:
$ sudo networksetup -createBond name [device1] [device2] [.]

To delete a bond:

$ sudo networksetup -deleteBond bond
To add a device to a bond:
$ sudo networksetup -addDeviceToBond device bond
To remove a device from a bond:
$ sudo networksetup -removeDeviceFromBond device bond

To list available bonds:

$ sudo networksetup -listBonds
To display a bond status:
$ sudo networksetup -showBondStatus bond
Managing AppleTalk Settings
AppleTalk is a suite of protocols developed to implement file sharing, mail service, and printing between Apple computers. To enable or disable AppleTalk, use the serversetup tool. To enable AppleTalk on a port:
$ serversetup -EnableAT [(devicename|"portname")]
If you dont provide an interface, en0 is assumed. To disable AppleTalk on a port:
$ serversetup -DisableAT [(devicename|"portname")]
To enable AppleTalk on en0:
$ serversetup -EnableDefaultAT
To disable AppleTalk on en0:
$ serversetup -DisableDefaultAT
To make AppleTalk active or inactive for a configuration:
$ sudo networksetup -setappletalk "configuration" (on|off)
To verify the AppleTalk state on en0:
$ serversetup -getDefaultATActive

> get State:/Network/Interface/en0/IPv4 > d.show
stores the information from the get command in a local dictionary variable called d. You can also watch or monitor a variable so that if its state changes scutil alerts you.
To quit the scutil session, enter quit at the prompt.

> quit

You can also manage system configuration parameters scutil using the --get and --set options. These provide a means of reporting and updating a group of persistent system preferences, including ComputerName, LocalHostName, or HostName. To set the hostname of a system:
$ sudo scutil --set HostName mycomputer.mac.com

mycomputer.mac.com

Description The new hostname value you want to set
To get the hostname of a system:
$ scutil --get HostName mycomputer.mac.com
For more information, see the scutil man page or enter help at the scutil prompt.
Changing Network Locations
A network location contains all network configuration settings for a specific network, such as Ethernet, AirPort, FireWire, or Bluetooth. Each location has a separate set of network settings. Mobile users who switch between networks have multiple locations set up on their computer and might need to switch between locations quickly. scselect allows you to access these configuration sets or locations. To view locations:

$ scselect

The computer responds with output similar to the following:
Defined sets include: (* == current set) * 0 (Automatic) 1 (AirPort) 2 (Home Office)
To change the location, enter the number of the location to switch to:

$ scselect 1

In this example, the network location switches to AirPort.
Working with Disks and Volumes
Use this chapter to learn the commands to initialize and test disks and volumes.
This chapter covers the commands used to manage, configure, initialize, and test disks and volumes.
Understanding Disks, Partitions, and the File System
Like UNIX, Mac OS X uses special files called device files, located in /dev, to keep track of the devices (disks, keyboards, monitors, network connections, and so on) attached to the computer. Device files for a disk are named /dev/diskn, where n is the number of the disk. For example, a computer with one drive would have a device file called /dev/disk0. If the computer has a second drive, the computer creates a second device file called /dev/disk1, and so on. Each drive that is divided into multiple partitions has a device file for each partition. The first partition on disk 0 is called /dev/disk0s1, the second partition is /dev/disk0s2, and so on. Although Mac OS X Server assigns a device name to each device, the files on a device are not accessed in this way. A virtual file system is created where all files on all devices appear to exist in a single hierarchy. This sets one root folder, and every file existing on the computer is under that folder. This is known as the Hierarchical File System (HFS+). The root folder can exist anywhere on a network as a shared resource.

Preventing a User from Logging In
Sometimes it is necessary to revoke a users ability to access the computer. This involves preventing the user from logging in and then terminating the users processes. The latter can be done by forcing the user to log out and then killing remaining processes, or by just killing the users processes. To prevent a user from logging in: m Disable the user account by entering the following command:
$ pwpolicy -a diradmin -u ajohnson -setpolicy isDisabled=1
Replace ajohnson with the short name of the user account and replace diradmin with the short name of your domain administrator account. Note: The pwpolicy command only works for LDAP/Password server users. For a local user, use Workgroup Manager or the Accounts pane of System Preferences.
To terminate a users processes: After disabling the user account, you need to kill the users active processes that are running on the directory server. WARNING: Unconditionally killing a users processes causes the user to lose unsaved data. 1 Make all processes clean up and exit by entering the following command, replacing ajohnson with the user name:
$ sudo killall -TERM -u ajohnson
2 Wait a few seconds to allow the previous command to execute; then, to terminate the users processes, enter the following command, replacing ajohnson with the user name:
$ sudo killall -9 -u ajohnson
For more information about terminating processes, see the killall man page. To reenable a disabled user account: m Enable the user account by entering the following command.
$ pwpolicy -a diradmin -u ajohnson -setpolicy isDisabled=0
Replace ajohnson with the short name of the user account and replace diradmin with the short name of your domain administrator account.
Verifying a Server Users Name, UID, or Password
To verify the name, UID, or password of a user in the servers local directory domain, use the following commands. Note: These tasks apply only to the local directory domain on the server. To see if a full name is in use:
$ sudo /System/Library/ServerSetup/serversetup -verifyRealName "longname"
The command displays a 1 if the name is in use, or a 0 if it isnt. To see if a short name is in use:

Note: In the example above, my_printer refers to the CUPS queue id.

Managing Print Service

To modify and manage Print service, use the serveradmin tool and the following commands that interact with CUPS.

Command (print:command=)

getJobs
Description Lists information about jobs in a queue. The name required for this command is the sharing name given to the queue by the administrator, as previously described. See Listing Jobs and Job Information on page 173. Finds the locations of Print service and job logs. See Viewing Print Service Log Files and Log Paths on page 175. Lists Print service queues. See Listing Queues on page 173. Holds or releases a job. The name required for this command is the sharing name given to the queue by the administrator, as previously described. See Holding and Releasing a Job on page 174. Pauses or releases a queue. The queue name required for this command is the sharing name given to the queue by the administrator, not the original printer name or the CUPS queue identifier. See Pausing and Releasing a Queue on this page. Equivalent to the standard serveradmin settings command, but also returns a setting indicating whether the service must be restarted. See Using the serveradmin Tool on page 50.

getQueues setJobState

setQueueState

Listing Queues

To list print service queues, use the serveradmin getQueues command.
$ sudo serveradmin command print:command = getQueues
Pausing and Releasing a Queue
You can use the serveradmin setQueueState command to pause or release a queue. To pause a queue:
$ sudo serveradmin command print:command = setQueueState print:state = PAUSED print:namesArray:_array_index:0 = queue Control-D
Description The name of the queue. To find the name of the queue, use the getQueues command and look for the value of the printer setting. See Listing Queues on page 173.

To release a queue:

Viewing Mail Service Logs
You can use tail or another file-listing tool to view the contents of Mail service logs. To view the latest entries in a log:
You can use the serveradmin getLogPaths command to see where Mail service logs are located. To view the log locations:
$ sudo serveradmin command mail:command = getLogPaths
mail:Server Log = <server-log> mail:Lists smtp = <delivery-log> mail:Amavisd Log = <amavis-log> mail:Virus DB Log = <freshclam-log> mail:Lists subscribe = <subscriptions-log> mail:Lists smtp-failure = <failures-log> mail:Lists post = <postings-log> mail:Lists error = <listerrors-log> mail:POP Log = <pop-log> mail:SMTP Log = <smtp-log> mail:Lists qrunner = <lists-log> mail:Virus Log = <clamav-log> mail:IMAP Log = <imap-log>

<server-log>

Description The location of the server log. Default = "/var/log/mailaccess.log" The location of the Mailing Lists Delivery log. Default = "/var/mailman/logs/smtp"

<delivery-log>

<amavis-log>
Description The location of the mail filtering log. Default = "/var/log/amavis.log" The location of the virus definition updates log. Default = "/var/log/freshclam.log" The location of the Mailing Lists Subscriptions log. Default = "/var/mailman/logs/subscribe" The location of the Mailing Lists Delivery Failures log. Default = "/var/mailman/logs/smtp-failure" The location of the Mailing Lists Postings log. Default = "/var/mailman/logs/post" The location of the Mailing Lists Error log. Default = "/var/mailman/logs/error" The location of the POP log. Default = "/var/log/mailaccess.log" The location of the server log. Default = "/var/log/mail.log" The location of the Mailing Lists log. Default = "/var/mailman/logs/qrunner" The location of the virus scanning log. Default = "/var/log/clamav.log" The location of the IMAP log. Default = "/var/log/mailaccess.log"

<freshclam-log>

<subscriptions-log>

<failures-log>

<postings-log>

<listerrors-log>

<pop-log>

<smtp-log>

<lists-log>

<clamav-log>

subnets:_array_id:<subnetID>: net_mask
Description The subnet mask for the subnet. Corresponds to the Subnet Mask field in the General pane of the subnet settings in Server Admin. The highest available IPv4 address for the subnet. Corresponds to the Ending IP Address field in the General pane of the subnet settings in Server Admin. The lowest available IPv4 address for the subnet. Corresponds to the Starting IP Address field in the General pane of the subnet settings in Server Admin. The network port for the subnet. Corresponds to the Network Interface pop-up menu in the General pane of the subnet settings in Server Admin. The NetBIOS Datagram Distribution Server IPv4 address. Corresponds to the NBDD Server field in the WINS pane of the subnet settings in Server Admin. The WINS node type. Can be set to: "" (not set; default) BROADCAST_B_NODE PEER_P_NODE MIXED_M_NODE HYBRID-H-NODE Corresponds to the NBT Node Type field in the WINS pane of the subnet settings in Server Admin. The primary WINS server used by clients. Corresponds to the WINS/NBNS Primary Server field in the WINS pane of the subnet settings in Server Admin. A domain name such as apple.com. Default = "" Corresponds to the NetBIOS Scope ID field in the WINS pane of the subnet settings in Server Admin. The secondary WINS server used by clients. Corresponds to the WINS/NBNS Secondary Server field in the WINS pane of the subnet settings in Server Admin.

net_range_end

net_range_start

selected_port_name

WINS_NBDD_server

WINS_node_type

WINS_primary_server

WINS_scope_id

WINS_secondary_server

Adding a DHCP Subnet

To add other subnets to your DHCP configuration, use the serveradmin settings command. You might already have a subnet for each port you enabled when you installed and set up the server. You can use the serveradmin settings command to check for subnets the server set up for you (see Viewing DHCP Service Settings on page 222). Note: Include the special first setting (ending with = create). This is how you tell to create the settings array with the specified subnet ID. To add a subnet:
$ sudo serveradmin settings dhcp:subnets:_array_id:subnetID = create dhcp:subnets:_array_id:subnetID:WINS_NBDD_server = nbdd-server dhcp:subnets:_array_id:subnetID:WINS_node_type = node-type dhcp:subnets:_array_id:subnetID:net_range_start = start-address dhcp:subnets:_array_id:subnetID:WINS_scope_id = scope-ID dhcp:subnets:_array_id:subnetID:dhcp_router = router dhcp:subnets:_array_id:subnetID:net_address = net-address dhcp:subnets:_array_id:subnetID:net_range_end = end-address dhcp:subnets:_array_id:subnetID:lease_time_secs = lease-time dhcp:subnets:_array_id:subnetID:dhcp_ldap_url:_array_index:0 = ldap-server dhcp:subnets:_array_id:subnetID:WINS_secondary_server = wins-server-2 dhcp:subnets:_array_id:subnetID:descriptive_name = description dhcp:subnets:_array_id:subnetID:WINS_primary_server = wins-server-1 dhcp:subnets:_array_id:subnetID:dhcp_domain_name = domain dhcp:subnets:_array_id:subnetID:dhcp_enabled = (yes|no) dhcp:subnets:_array_id:subnetID:dhcp_domain_name_server:_array_index:0 = dns-server-1 dhcp:subnets:_array_id:subnetID:dhcp_domain_name_server:_array_index:1 = dns-server-2 dhcp:subnets:_array_id:subnetID:net_mask = mask dhcp:subnets:_array_id:subnetID:selected_port_name = port Control-D

nat:natLog = <nat-log>

<nat-log>

Description The location of the NAT service log. Default = /var/log/alias.log

Managing VPN Service

A Virtual Private Network (VPN) is two or more computers or networks (nodes) connected by a private link of encrypted data. This link simulates a local connection, as if the remote computer were attached to the local area network (LAN).
VPNs allow users at home or away from the LAN to securely connect to it using any network connection, such as the Internet. From the users perspective, the VPN connection appears as a dedicated private link.
Starting and Stopping VPN Service
$ sudo serveradmin start vpn
$ sudo serveradmin stop vpn
Checking the Status of VPN Service
To see a summary status of service:
$ sudo serveradmin status vpn
To see a detailed status of service:
$ sudo serveradmin fullstatus vpn
Viewing VPN Service Settings
$ sudo serveradmin settings vpn:setting
$ sudo serveradmin settings vpn
Changing VPN Service Settings
$ sudo serveradmin settings vpn:setting = value
Description A VPN service setting. To see a list of available settings, enter
or see Available VPN Service Settings on page 242.
$ sudo serveradmin settings vpn:setting = value vpn:setting = value vpn:setting = value [.] Control-D
Available VPN Service Settings
To change settings for VPN service, use the following parameters with the serveradmin tool.

Parameter (vpn:Servers:)

com.<name>.ppp.l2tp: Server:VerboseLogging com.<name>.ppp.l2tp: Server:MaximumSessions com.<name>.ppp.l2tp: Server:LogFile com.<name>.ppp.l2tp: IPSec:IPSecSharedSecretEncryption com.<name>.ppp.l2tp: IPSec:SharedSecret com.<name>.ppp.l2tp: IPSec:LocalIdentifier com.<name>.ppp.l2tp: IPSec:LocalCertificate com.<name>.ppp.l2tp: IPSec:AuthenticationMethod com.<name>.ppp.l2tp: IPSec:IdentifierVerification com.<name>.ppp.l2tp: IPSec:RemoteIdentifier com.<name>.ppp.l2tp: L2TP:Transport com.<name>.ppp.l2tp: IPv4:DestAddressRanges com.<name>.ppp.l2tp: IPv4:OfferedRouteMasks com.<name>.ppp.l2tp: IPv4:OfferedRouteAddresses com.<name>.ppp.l2tp: IPv4:OfferedRouteTypes com.<name>.ppp.l2tp: IPv4:ConfigMethod com.<name>.ppp.l2tp: DNS:OfferedSearchDomains com.<name>.ppp.l2tp: DNS:OfferedServerAddresses com.<name>.ppp.l2tp: Interface:SubType

Preface About This Guide

Help Viewer automatically retrieves and caches the most recent server help topics from the Internet. When not connected to the Internet, Help Viewer displays cached help topics.
Mac OS X Server Administration Guides
Getting Started covers installation and setup for standard and workgroup configurations of Mac OS X Server. For advanced configurations, Server Administration covers planning, installation, setup, and general server administration. A suite of additional guides, listed below, covers advanced planning, setup, and management of individual services. You can get these guides in PDF format from the Mac OS X Server documentation website: www.apple.com/server/documentation
This guide. Getting Started and Mac OS X Server Worksheet Command-Line Administration File Services Administration iCal Service Administration iChat Service Administration Mac OS X Security Configuration Mac OS X Server Security Configuration Mail Service Administration Network Services Administration Open Directory Administration Podcast Producer Administration Print Service Administration QuickTime Streaming and Broadcasting Administration Server Administration tells you how to: Install Mac OS X Server and set it up for the first time. Install, set up, and manage Mac OS X Server using UNIX commandline tools and configuration files. Share selected server volumes or folders among server clients using the AFP, NFS, FTP, and SMB protocols. Set up and manage iCal shared calendar service. Set up and manage iChat instant messaging service. Make Mac OS X computers (clients) more secure, as required by enterprise and government customers. Make Mac OS X Server and the computer its installed on more secure, as required by enterprise and government customers. Set up and manage IMAP, POP, and SMTP mail services on the server. Set up, configure, and administer DHCP, DNS, VPN, NTP, IP firewall, NAT, and RADIUS services on the server. Set up and manage directory and authentication services, and configure clients to access directory services. Set up and manage Podcast Producer service to record, process, and distribute podcasts. Host shared printers and manage their associated queues and print jobs. Capture and encode QuickTime content. Set up and manage QuickTime streaming service to deliver media streams live or on demand. Perform advanced installation and setup of server software, and manage options that apply to multiple services or to the server as a whole.

This guide. System Imaging and Software Update Administration Upgrading and Migrating User Management Web Technologies Administration Xgrid Administration and High Performance Computing Guide Mac OS X Server Glossary
tells you how to: Use NetBoot, NetInstall, and Software Update to automate the management of operating system and other software used by client computers. Use data and service settings from an earlier version of Mac OS X Server or Windows NT. Create and manage user accounts, groups, and computers. Set up managed preferences for Mac OS X clients. Set up and manage web technologies, including web, blog, webmail, wiki, MySQL, PHP, Ruby on Rails, and WebDAV. Set up and manage computational clusters of Xserve systems and Mac computers. Learn about terms used for server and storage products.
Viewing PDF Guides Onscreen
While reading the PDF version of a guide onscreen: Show bookmarks to see the guides outline, and click a bookmark to jump to the corresponding section. Search for a word or phrase to see a list of places where it appears in the document. Click a listed place to see the page where it occurs. Click a cross-reference to jump to the referenced section. Click a web link to visit the website in your browser.

Printing PDF Guides

If you want to print a guide, you can take these steps to save paper and ink: Save ink or toner by not printing the cover page. Save color ink on a color printer by looking in the panes of the Print dialog for an option to print in grays or black and white. Reduce the bulk of the printed document and save paper by printing more than one page per sheet of paper. In the Print dialog, change Scale to 115% (155% for Getting Started). Then choose Layout from the untitled pop-up menu. If your printer supports two-sided (duplex) printing, select one of the Two-Sided options. Otherwise, choose 2 from the Pages per Sheet pop-up menu, and optionally choose Single Hairline from the Border menu. (If youre using Mac OS X v10.4 or earlier, the Scale setting is in the Page Setup dialog and the Layout settings are in the Print dialog.) You may want to enlarge the printed pages even if you dont print double sided, because the PDF page size is smaller than standard printer paper. In the Print dialog or Page Setup dialog, try changing Scale to 115% (155% for Getting Started, which has CDsize pages).

Defining Realms

When you define a realm, which is typically a folder (or file system), the access privileges you set for the realm apply to all contents of that folder. If a new realm is defined for a folder in the existing realm, only the new realm privileges apply to that folder and its contents. For information about creating realms and setting access privileges, see Using Realms to Control Access on page 40. Note: When an assigned user or group possesses fewer permissions than the permissions that have been assigned to user Everyone, that user or group is deleted upon a refresh. This happens because the access assigned to Everyone preempts the access assigned to specific users or groups with fewer permissions than those possessed by Everyone. The greater permissions always take precedence. Consequently, the list of assigned users and groups with fewer permissions are not saved in the Realms pane upon refresh if their permissions are determined to be preempted by the permissions assigned to Everyone. After the refresh the names are no longer listed in the list on the right in the Realms pane. Also, for a brief period of time, user Everyone will switch its displayed name to "no-user.
Understanding Multipurpose Internet Mail Extension (MIME)
Multipurpose Internet Mail Extension (MIME) is an Internet standard for specifying what happens when a web browser requests a file with certain characteristics. You can choose the response you want the web server to make based on the files suffix. Your choices depend partly on what modules you have installed on your web server. Each combination of a file suffix and its associated response is known as a MIME type mapping.

MIME Suffixes

A suffix describes the type of data in a file. Here are some examples: txt for text files cgi for Common Gateway Interface files gif for GIF (graphics) files php for PHP: Hypertext Preprocessor (embedded HTML scripts) used for Webmail, and so on tiff for TIFF (graphics) files Mac OS X Server includes a default set of MIME type suffixes. This set includes all the suffixes in the mime.types file distributed with Apache, with a few additions. If a suffix you need is not listed or does not have the behavior you want, use Server Admin to add the suffix to the set or to change its behavior.
Note: Do not add or change MIME suffixes by editing configuration files.

7 Click Save.

Configuring Proxy Settings
You use the Proxy settings pane in Web service to configure a forward proxy. A forward proxy is located between the web server and client browsers and passes requests for information between clients and server. The client must be configured to use the forward proxy to access other sites. A forward proxy is commonly used to provide Internet access to internal client computers that are restricted by a firewall. A forward proxy lets users verify a local server for frequently used files. A forward proxy can be used to block access to specific sites for internal clients and can improve performance. You can also use a forward proxy to speed response times and reduce network traffic. The proxy stores recently accessed files in a cache on your web server. Browsers on your network verify the cache before retrieving files from more distant servers. For additional security you should restrict access to your server by setting up this forward proxy. This is particularly true if your server hosts internal and external websites. If your web server is set up to act as a proxy, you can prevent the server from caching objectionable websites. Important: To take advantage of this feature, client computers must specify your web server as their proxy server in their browser preferences. When setting up a forward proxy, make sure you create and enable a website for the proxy. You might want to disable logging on the proxy site or configure the site to record its access log in a separate file from your other sites access logs. The site does not need to be on port 80 but setting up web clients is easier if it is because browsers use port 80 by default. Mac OS X Server v10.5 provides forward and reverse proxy. The reverse proxy is configured in the Web service Sites pane. For information about setting up a reverse proxy, see Setting Up a Reverse Proxy on page 47. To configure Web service forward proxy settings: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select Web. 4 Click Settings, then click Proxy. 5 Select the Enable Forward Proxy checkbox. If a forward proxy server is enabled, each site on the server can be used as the proxy.
6 Select the Control Access To Proxy checkbox to limit access and then enter the domain name that is permitted access in the Allowed Domain field. Generally, when limiting who can use your web server as a proxy, limit access to a specific domain. Users in that domain obtain access. 7 In the Cache Folder field, enter the pathname for the cache folder. You can also click the Browse button and browse for the folder you want to use. If you are administering a remote server, File service must be running on the remote server to use the Browse button. If you change the folder location from the default, you must select the new folder in Finder. Choose File > Get Info, and change the owner and group to www. 8 Set the disk cache target size and set an interval for emptying the cache. When the cache reaches this size, the oldest files are deleted from the cache folder. 9 To add a host to block, click the Add (+) button and enter its URL. Add the names of all hosts you want to block. You can import a list of websites by dragging the list to the list of blocked hosts. The list must be a text file with the host names separated by commas or tabs (also known as csv and tsv strings). Make sure the last entry in the file is terminated with a carriage return/line feed; otherwise, it is overlooked. 10 Click Save.

To use a realm to control website access: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select Web. 4 Click Sites, then select the website in the list. 5 Click Realms below the websites list. 6 Click the Add (+) button to create a realm. The realm is the part of the website users can access. 7 In the Realm Name field, enter the realm name. This is the name users see when they log in to the website. 8 From the Authentication pop-up menu, choose a method of authentication. Basic authentication is on by default. Dont use basic authentication for sensitive data because it sends your password to the server unencrypted. Digest authentication is more secure than basic authentication because it uses an encrypted hash of your password. Kerberos authentication is the most secure because it implements server certificates to authenticate. If you want Kerberos authentication for the realm, you must join the server to a Kerberos domain. 9 Enter the realm location or folder you are restricting access to: Choose Location from the pop-up menu and enter a URL to the location in the website that you want to restrict access to. Choose Folder from the pop-up menu and enter the path to the folder that you want to restrict access to. You can also click the Browse button to locate the folder you want to use. 10 Click OK. 11 Select the new realm and click Add (+) to open the Users & Groups panel. To switch between the Users list and the Groups list, click Users or Groups in the panel. 12 To add users or groups to a realm, drag users to the list on the right in the Realms pane. When users or members of a group youve added to the realm connect to the site, they must supply their user name and password. 13 Limit realm access to specified users and groups by setting the following permissions using the up and down arrows in the Persmissions column. Browse Only: Permits users or groups to browse the website.
Browse and Read WebDAV: Permits users or groups to browse the website and also read the website files using WebDAV. Browse and Read/Write WebDAV: Permits users or groups to browse the website and also read and write to website files using WebDAV. None: Prevents users or groups from using any permissions. 14 Click Save. Use the Realms pane to delete a user or group by selecting the name and clicking the Delete () button.

Enabling Secure Sockets Layer (SSL)
Secure Sockets Layer (SSL) provides security for a site and its users by authenticating the server, encrypting information, and maintaining message integrity. SSL is a per-site setting that lets you send encrypted, authenticated information across the Internet. For example, if you want to permit credit card transactions through a website, you can protect the information thats passed to and from that site. The SSL layer is below application protocols (for example, HTTP) and above TCP/IP. This means that when SSL is operating on the server and on the client computer, all information is encrypted before being sent. The Apache web server in Mac OS X Server uses a public key-private key combination to protect information. A browser encrypts information using a public key provided by the server. Only the server has a private key that can decrypt that information. The web server supports SSLv2, SSLv3, and TLSv1. More information about these protocol versions is available at www.modssl.org.
When SSL is implemented on a server, a browser connects to it using the https prefix in the URL, rather than http. The s indicates that the server is secure. When a browser initiates a connection to an SSL-protected server, it connects to a specific port (443) and sends a message that describes the encryption ciphers it recognizes. The server responds with its strongest cipher, and the browser and server then continue exchanging messages until the server determines the strongest cipher that it and the browser can recognize. The server then sends its certificate (an ISO X.509 certificate) to the browser. This certificate identifies the server and uses it to create an encryption key for the browser to use. At this point a secure connection has been established and the browser and server can exchange encrypted information. Before you can enable SSL protection for a website, you must obtain the proper certificates. For detailed information about certificates and their management, see Server Administration. To set up SSL for a website: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select Web. 4 Click Sites, then select the website in the list. 5 Click Security below the websites list. 6 In the Security pane, select Enable Secure Sockets Layer (SSL). When you turn on SSL, a message appears, noting that the port is changed to 443. 7 In the Certificate pop-up menu, choose the certificate you want. If the certificate is protected by a passphrase, the name of the certificate must match the virtual host name. If the names dont match, Web service wont restart. 8 If you choose Custom Configuration or want to edit a certificate, you might have to do the following: a Click the Edit (/) button and supply the correct information in each field for the certificate. b If you received a ca.crt file from the certificate authority, click the Edit (/) button and paste the text from the ca.crt file in the Certificate Authority File field. Note: The ca.crt file might be required but might not be sent directly to you. This file must be available on the website of the certificate authority. c In the Private Key Passphrase field, enter a passphrase and click OK. 9 Click Save.

About Wiki Pages

The following is a list of the wiki pages and their description: Groups page: Page that links to all groups hosted by the wiki website. Wiki Home page: The home page of a groups wiki. Contains links to pages, a group calendar, group blog, and search, as well as to the default sidebars (for example, "What's hot" and "Recent Changes"). Document pages: Pages that group members create. They are dynamically linked to and from other webpages and are found by using search and tags. Calendar pages: Pages that show a group calendar that uses iCal service to provide a shared calendar to group members. For more information on iCal service, see iCal Service Administration. Mailing list pages: Pages that provide a web archive of a group's mailing list traffic. For more information about Webmail, see Chapter 5, Configuring and Managing Webmail. Blog Pages: Pages that show a user or group blog. Blogs are created and updated when users or members of the group (that have Read and Write access to a group blog) add comments to the blogs. For more information about blogs, see Setting Up User and Group Blogs on page 75.

About Wiki Security

The level of website security determines the level of wiki security. Wiki security is established when the website that the wiki is configured on is secure. Methods you can use to help secure data moving to and from your wiki include the following: Set up SSL for the website your wiki is running on. SSL provides security for a site and its users by authenticating the server, encrypting information, and maintaining message integrity. For more information, see Enabling Secure Sockets Layer (SSL) on page 43. Restrict user and groups that can create wiki pages on your website by adding users and groups to the Web services list. For more information, see Enabling Web Calendar Service for a Website on page 72.
About Wiki File and Folder Hierarchy
By default wiki content is stored in the /Library/Collaboration/ folder. This folder can be changed in the Web service Settings Web Services pane in Server Admin. The following list shows the default wiki file and folder hierarchy. This includes where all wiki files are stored and the folder structure for the wiki content. In the list, groupname is the name of the group, pagename is the name of the wiki page, and page is the name of the webpage. /Library/Collaboration/ contains all files for the wiki.
Chapter 4 Creating and Managing Wikis and Blogs
/Library/Collaboration/Groups/groupname/ contains all files for one groups services. /Library/Collaboration/Groups/groupname/wiki/pagename.page/ contains the component files of a wiki page. /Library/Collaboration/Groups/groupname/wiki/pagename.page/page.html contains the main text of the wiki (html content). /Library/Collaboration/Groups/groupname/wiki/pagename.page/page.plist contains the metadata for the wiki page. /Library/Collaboration/Groups/groupname/wiki/pagename.page/revisions.db contains the version history database for that wiki page. /Library/Collaboration/Groups/groupname/pagename.page/images/ contains the images for that wiki page. /Library/Collaboration/Groups/groupname/pagename.page/attachments/ contains all attachments for that wiki page.

Wiki Setup Overview

Here is an overview of the basic steps for setting up a wiki. Step 1: Configure your web server The default configuration works for most web servers that host a single website but you can configure all basic features of Web service and websites using Server Admin. For more information, see Chapter 2, Working with Web Service. Before you create and configure wikis or blogs, set up default web services settings. For details, see Configuring Web Services Settings on page 29. Step 2: Set up your website With your web service configured and running, you can create websites. Creating a website establishes the framework that you use to provide web-hosted content in various formats, including wikis and blogs. For details, see Chapter 3, Creating and Managing Websites. Step 3: Enable wiki web services for your website To create a wiki, you must enable the wiki web service on your website. For details, see Enabling Web Calendar Service for a Website on page 72. Step 4: Create groups for the wiki After the wiki web service is enabled on your website, you must create groups in Workgroup Manager or Directory and give them access to the wiki web service for the wiki site. For more information about using Directory, see Directory help. Wikis are provisioned for groups as they are created and enabled for web services in Workgroup Manager. You can modify the Write and View permissions for users within the group for wiki pages. For details, see User Management.
Step 5: Connect to your wiki To make sure the wiki is working properly, open your browser and try to connect to it over the Internet. For details, see Connecting to a Wiki on page 65.

Setting Up a Wiki

The following sections provide instructions for setting up a wiki on your website.
Enabling Wiki Web Services for a Website
You can enable wiki web services on your website. In addition, blogs, calendaring, and mailing list web services are available for your site. Wiki will not work without a local Open Directory master. Your server can be connected to another directory server simultaneously, but for wiki to work, your server must be an Open Directory master. For more information, see Open Directory Administration. To enable wiki services on your website: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select Web. 4 Click Sites, then select the website in the list. 5 Click Web Services below the websites list. 6 Select the Blog checkbox to enable user blogs for your website. This gives users the ability to create and maintain personal blog pages. A blog is a chronological journal on your website that is updated with content added by users. For more information, see Setting Up User and Group Blogs on page 75. 7 Select the Wiki and blog checkbox to enable group website functionality. This website functionality makes it easy for groups of people to create and distribute information in their own shared websites. This also enables group blogs on your wiki pages. 8 If you want calendar functionality for your website, select the Web calendar checkbox. Users can access a group calendar to track meetings and deadlines. For details, see Setting Up a Web Calendar on page 72. 9 If you want mailing list functionality on your website, select the Mailing list web archive checkbox. A mailing list is a discussion group that uses mass email to facilitate communication. For details, see Setting Up Mailing List Web Archives on page 80.

Setting Blog SACL Permissions for Users
Web services administrators can use service access control lists (SACLs) to specify which users have access to blogs. Use Server Admin to set SACL permissions. Important: To change SACL settings for blogs, you must use the server interface, not the Web interface. To set user SACL permissions for a blog: 1 Open Server Admin and connect to the server. 2 Select the server. The list of services appears. 3 Click Settings. 4 Click Access. 5 Click Services, if it is not already displayed. 6 Select the level of restriction that you want for the services. To restrict access to all services, select For all services. To set access permissions for blogs, select For selected services below and then select Blog from the Service list. 7 Select the level of restriction you want for users and groups. To provide unrestricted access, click Allow all users and groups. To restrict access to specific users and groups, select Allow only users and groups below, click the Add (+) button to open the Users and Groups pane, and then drag users and groups to the list. 8 Click Save.
Configuring and Managing Webmail
This chapter shows you how to enable Webmail for the websites on your server in order to provide access to basic mail operations via a web connection.
Webmail adds basic mail functions to your website. If your web service hosts more than one website, Webmail can provide access to mail service on all sites. The mail service looks the same on all sites.

Webmail Overview

The Webmail software is included in Mac OS X Server and is disabled by default. The Webmail software is based on SquirrelMail (v1.4.9a), which is a collection of open source scripts run by the Apache server. For more information about SquirrelMail, see www.squirrelmail.org.

Webmail User Services

If you enable webmail, you users can: Compose and send messages Receive messages Forward or reply to received messages Maintain a signature that is appended to each sent message Create, delete, and rename folders and move messages between folders Attach files to outgoing messages Retrieve attached files from incoming messages Manage a private address book Set webmail preferences, including the color scheme displayed in the web browser Users access the Webmail page of your website by appending /webmail to the URL of your site (for example, http://mysite.example.com/webmail/).

Starting WebObjects Service
You start WebObjects service from Server Admin. To start WebObjects service: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select WebObjects. 4 Click Start WebObjects (below the Servers list). The service runs until you stop it and restarts if your server is restarted. From the Command Line You can also start or stop WebObjects using the serveradmin command in Terminal by entering the following commands:
$ serveradmin start webobjects $ serveradmin stop webobjects
Checking the Status of WebObjects Service
You can use Server Admin to monitor WebObjects service. To check the status of WebObjects service: 1 Open Server Admin and connect to the server.
2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select WebObjects. 4 Click Overview to see if WebObjects service is running, the time it started if it is running, and to see if Monitor is running.
Stopping WebObjects Service
You can use Server Admin to stop WebObjects service. To stop WebObjects service: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select WebObjects. 4 Click Stop WebObjects (below the Servers list).

Opening the Monitor

Monitor is a web-based tool that helps you manage and monitor applications running on WebObjects service. You use this tool to set up applications for deployment through your web server and to control load balancing across multiple web servers. For more information, open Monitor and select Help. To open Monitor: 1 Open Server Admin and connect to the server. 2 Click the triangle to the left of the server. The list of services appears. 3 From the expanded Servers list, select WebObjects. 4 Click Settings and select the Enable Monitor checkbox. 5 Click Save. 6 Open a web browser and enter the address for Monitor: http://localhost:<Monitor port>

Glossary

IP Internet Protocol. Also known as IPv4. A method used with Transmission Control Protocol (TCP) to send data between computers over a local network or the Internet. IP delivers data packets and TCP keeps track of data packets. IP address A unique numeric address that identifies a computer on the Internet. JavaScript A scripting language used to add interactivity to webpages. JBoss A full-featured Java application server that provides support for Java 2 Platform, Enterprise Edition (J2EE) applications. Kerberos realm The authentication domain comprising the users and services that are registered with the same Kerberos server. The registered users and services trust the Kerberos server to verify each others identities. local hostname A name that designates a computer on a local subnet. It can be used without a global DNS system to resolve names to IP addresses. It consists of lowercase letters, numbers, or hyphens (except as the last characters), and ends with.local (For example, bills-computer.local). Although the default name is derived from the computer name, a user can specify this name in the Sharing pane of System Preferences. It can be changed easily, and can be used anywhere a DNS name or fully qualified domain name is used. It can only resolve on the same subnet as the computer using it. multicast DNS A protocol developed by Apple for automatic discovery of computers, devices, and services on IP networks. Called Bonjour (previously Rendezvous) by Apple, this proposed Internet standard protocol is sometimes referred to as ZeroConf or multicast DNS. For more information, visit www.apple.com or www.zeroconf.org. To see how this protocol is used in Mac OS X Server, see local hostname. MySQL An open source relational database management tool frequently used by web servers. open source A term for the cooperative development of software by the Internet community. The basic principle is to involve as many people as possible in writing and debugging code by publishing the source code and encouraging the formation of a large community of developers who will submit modifications and enhancements. PHP PHP Hypertext Preprocessor (originally Personal Home Page). A scripting language embedded in HTML thats used to create dynamic webpages. port A sort of virtual mail slot. A server uses port numbers to determine which application should receive data packets. Firewalls use port numbers to determine whether data packets are allowed to traverse a local network. Port usually refers to either a TCP or UDP port.

user content 39, 57, 59, 107 viewing 31 See also blog service; WebDAV; wikis web technologies overview 9, 15, 16, 17 wikis and blog service 62, 64 calendar feature 72, 73, 74 connections 65 customizing 70, 71 definition 48 enabling 64 file organization 62, 68, 69
help resources 71 logs 42 overview 61, 62 page management 66, 67, 68, 69, 70 security 62 settings 65 setup overview 63, 64 themes 29, 71 wildcard, website aliases 45 wireframe theme, wiki 71 wotaskd daemon 84