## bootstrap_completed

Server Interface - Inform bootstrap server that initialization is complete.

### SYNOPSIS

    kern_return_t   bootstrap_completed
                    (mach_port_t                     bootstrap_port,
                     task_t                                    task);

### PARAMETERS

bootstrap_port
  The port representing the calling task's bootstrap server.

task
  This parameter represents the calling task.

### DESCRIPTION

This interface allows a given server task to inform the bootstrap server that it is fully initialized and ready to handle requests. Upon receiving such notification, the bootstrap server can initialize any additional servers that may require services provided by the previously initialized server.

Note the following: not all servers that may be invoked by the bootstrap server send this message upon startup. If the bootstrap server is told to wait for this message before spawning further servers (via setting a flag in the bootstrap.conf file) and the server just invoked never sends this message, the bootstrap server will wait forever.

### NOTES

Currently, this interface is used exclusively by the default pager server so that the bootstrap server can defer initializing the OS server until the default pager is in place. (In small memory configurations, an OS server may not be able to initialize successfully unless the default pager is ready to handle paging requests.)

### RETURN VALUES

KERN_SUCCESS
  The bootstrap server has updated the calling server's state with respect to bootstrap completion.

KERN_INVALID_ARGUMENT
  The bootstrap server does not recognize the calling server (the task specified by the task parameter).

### RELATED INFORMATION

Functions: