Haiku/haiku
Haiku/haiku
1
0
Fork 0
mirror of https://review.haiku-os.org/haiku synced 2025-01-19 04:58:51 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
9939ccadff
haiku/data/launch/system

92 lines
1.5 KiB
Plaintext
Raw Normal View History

The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
service x-vnd.Haiku-registrar {
launch /system/servers/registrar
registrar: implemented auth port via launch_daemon. * get_roster_port_name() is no longer needed. * This also removes the app_server restart code from the debug server -- this will be done by the launch_daemon in the future.
2015-05-11 09:10:24 +02:00
port auth {
capacity 100
}
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-app_server {
launch /system/servers/app_server
}
service x-vnd.Haiku-debug_server {
launch /system/servers/debug_server
}
service x-vnd.Haiku-package_daemon {
launch /system/servers/package_daemon
}
launch_daemon: added support for arbitrary ports. * Dropped "create_port" -- this is now the default for services. * Additionally (or alternatively, if you use the "legacy" mode), you can now create named ports, and specify their capacity. * Added convenience methods to BLaunchRoster that automatically use the signature of the current be_app.
2015-04-21 18:40:26 +02:00
service x-vnd.Haiku-SystemLogger {
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
launch /system/servers/syslog_daemon
launch_daemon: added support for arbitrary ports. * Dropped "create_port" -- this is now the default for services. * Additionally (or alternatively, if you use the "legacy" mode), you can now create named ports, and specify their capacity. * Added convenience methods to BLaunchRoster that automatically use the signature of the current be_app.
2015-04-21 18:40:26 +02:00
port logger {
capacity 256
}
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-mount_server {
launch /system/servers/mount_server
}
service x-vnd.Haiku-media_server {
launch /system/servers/media_server
no_safemode
launch_daemon: added support for arbitrary ports. * Dropped "create_port" -- this is now the default for services. * Additionally (or alternatively, if you use the "legacy" mode), you can now create named ports, and specify their capacity. * Added convenience methods to BLaunchRoster that automatically use the signature of the current be_app.
2015-04-21 18:40:26 +02:00
legacy
launch_daemon: Correctly fix #12289 as pointed out by Axel. - Rather than depending just on mount_server's launch, instead use a condition that waits for the volumes mounted event. Had missed the existence of this one previously.
2015-08-08 23:12:17 +02:00
on {
initial_volumes_mounted
}
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-midi_server {
launch /system/servers/midi_server
no_safemode
midi_server: Converted to BServer, launched on demand.
2015-10-14 21:47:54 +02:00
on_demand
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-mail_daemon {
launch /system/servers/mail_daemon -E
no_safemode
launch_daemon: added support for arbitrary ports. * Dropped "create_port" -- this is now the default for services. * Additionally (or alternatively, if you use the "legacy" mode), you can now create named ports, and specify their capacity. * Added convenience methods to BLaunchRoster that automatically use the signature of the current be_app.
2015-04-21 18:40:26 +02:00
legacy
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
Add missing launch definition for net_server.
2015-07-22 23:19:02 +02:00
service x-vnd.Haiku-net_server {
launch /system/servers/net_server
no_safemode
legacy
}
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
service x-vnd.Haiku-cddb_daemon {
launch /system/servers/cddb_daemon
no_safemode
launch_daemon: added support for arbitrary ports. * Dropped "create_port" -- this is now the default for services. * Additionally (or alternatively, if you use the "legacy" mode), you can now create named ports, and specify their capacity. * Added convenience methods to BLaunchRoster that automatically use the signature of the current be_app.
2015-04-21 18:40:26 +02:00
legacy
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-print_server {
launch /system/servers/print_server
no_safemode
print_server: Converted to launch_daemon, run on demand only. * Seems to work fine, although it should probably also be triggered when there are still jobs in the queue -- someone more knowledgeable might want to chime in here, please :-) * If this turns out to be problematic, we can just drop the "on_demand" job config again.
2015-10-13 16:37:16 +02:00
on_demand
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-notification_server {
launch /system/servers/notification_server
no_safemode
notification_server: Converted to BServer, launch on demand.
2015-10-14 22:00:47 +02:00
on_demand
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
service x-vnd.Haiku-power_daemon {
launch /system/servers/power_daemon
no_safemode
launch_daemon: added support for arbitrary ports. * Dropped "create_port" -- this is now the default for services. * Additionally (or alternatively, if you use the "legacy" mode), you can now create named ports, and specify their capacity. * Added convenience methods to BLaunchRoster that automatically use the signature of the current be_app.
2015-04-21 18:40:26 +02:00
legacy
The beginnings of a launch_daemon for Haiku. * This will be heavily inspired by Apple's launchd, as well as systemd -- for now it really doesn't do a whole lot, though. * What works so far: the configuration files are read, parsed, and the jobs created. * The jobs are even initialized, and their message ports created. * BApplication now retrieves a previously created port from the launch_daemon for use with BServer. * Only the registrar actually uses this for now.
2015-04-02 11:42:35 +02:00
}
Boot the system via launch_daemon. * This is actually working already, although we cannot reproduce all the features of the former Bootscript yet. This is without any dependency support in launch_daemon. * All shell activity like cleaning out /tmp, setting up the environment, setting the time, etc. is not yet working.
2015-04-15 18:14:22 +02:00
Added post-install script, and start UserBootscript again. * This is the final missing piece of the former boot process. * Removed the unused Bootscript, and Bootscript.cd files.
2015-07-17 22:15:38 +02:00
job post-install {
launch /bin/sh /system/boot/PostInstallScript
if file_exists /boot/system/settings/fresh_install
}
launch_daemon: Improved target support. * You can now put jobs/services into a target. * Instead of having Login started as part of the normal boot process, it's now in the "login" target. * The app_server now launches the login target when a login becomes available (ie. during startup, but that could be improved later on).
2015-06-15 18:50:04 +02:00
target login {
Added autologin command, and use it by default. * This will handle our current single-user login needs. * Removed Login from the minimum image again.
2015-07-06 08:24:21 +02:00
job x-vnd.Haiku-autologin {
launch /system/bin/autologin
launch_daemon: Improved target support. * You can now put jobs/services into a target. * Instead of having Login started as part of the normal boot process, it's now in the "login" target. * The app_server now launches the login target when a login becomes available (ie. during startup, but that could be improved later on).
2015-06-15 18:50:04 +02:00
}
Boot the system via launch_daemon. * This is actually working already, although we cannot reproduce all the features of the former Bootscript yet. This is without any dependency support in launch_daemon. * All shell activity like cleaning out /tmp, setting up the environment, setting the time, etc. is not yet working.
2015-04-15 18:14:22 +02:00
}
Copy Permalink