 |
|
|
|
|
|
||
 |
|
||
|
|
||
|
||||||||||||||
|
| < Previous PageNext Page > |
If you are writing only kernel code, contexts are largely irrelevant (unless you are creating a new context, of course). However, kernel developers frequently need to write a program that registers itself in the startup context in order to provide some level of driver communication. For example, you could write a user-space daemon that brokers configuration information for a sound driver based on which user is logged in at the time.
In the most general case, the problem of starting an application
in the startup context can be solved by creating a startup script
for your daemon, which causes it to be run in the startup context
after the next reboot. However, users generally do not appreciate
having to reboot their computers to install a new driver. Asking
the user to connect to his or her own computer with ssh to
execute a script is probably not reasonable, either.
The biggest problem with forcing a reboot, of course, is that users often install several programs at once. Rebooting between each install inconveniences the end user, and has no other benefit. For that reason, you should not force the user to restart. Instead, you should offer the user the option, noting that the software may not work correctly until the user restarts. While this does not solve the fundamental problem, it does at least minimize the most common source of complaints.
There are a number of ways to force a program to start in
the startup context without rebooting or using ssh.
However, these are not robust solutions, and are not recommended.
A standard API for starting daemons is under consideration. When
an official API becomes available, this chapter will be updated
to discuss it.
| < Previous PageNext Page > |
Last updated: 2006-11-07
 |
||
|
|
|
|
| ||
| ||
Get information on Apple products.
Visit the Apple Store online or at retail locations. 1-800-MY-APPLE Copyright © 2007 Apple Inc. All rights reserved. | Terms of use | Privacy Notice |
