Searched +hist:7 +hist:cd19b7e (Results 1 - 9 of 9) sorted by relevance
| /haiku/docs/user/app/ | ||
| H A D | LaunchRoster.dox | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| /haiku/src/servers/launch/ | ||
| H A D | Events.h | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| H A D | Events.cpp | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| H A D | Job.h | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| H A D | Job.cpp | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| H A D | LaunchDaemon.cpp | diff 7d2a6f2d Wed Feb 16 21:02:41 MST 2022 Augustin Cavalier <waddlesplash@gmail.com> launch_daemon: Rework how user-session spawning functions. * Instead of fork()ing, which leaks memory (and runs a second BApplication inside the Run() of the original one, which was the source of a TODO), use posix_spawn to start a second process altogether. * Move session initialization code to the new user_main(), invoked from main() if we are starting a user session. * Send event registration messages to the new session daemon in _HandleRegisterSessionDaemon, as the child no longer has access to the old events list from before fork()ing and must receive it. The last of these fixes a race: previously, if an event was registered or triggered between when the child (user) launch_daemon was fork()ed off the parent and when it registered with the root launch_daemon, those events were "lost" and would never be forwarded to the child. That happened not altogether infrequently for some people (myself included) especially in virtual machines for the "initial_volumes_mounted" event, which was the most common remaining cause of "boot hangs on rocket" or "boots to blue screen with only mouse cursor" problems. So, in addition to being cleaner overall and resolving a number of TODOs, this also fixes #17365. Change-Id: I1ea28cba8938a38b3c27685d7f3943f596cfe7ec Reviewed-on: https://review.haiku-os.org/c/haiku/+/4968 Reviewed-by: waddlesplash <waddlesplash@gmail.com> Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> diff 7f4c5a1f Thu Sep 30 11:25:54 MDT 2021 Augustin Cavalier <waddlesplash@gmail.com> launch_daemon: Do not return errors from RegisterExternalEvent. We will pick up events that have no match later on, and if we return an error here, it will prevent the job from being initialized, which we definitely do not want. Fixes #17291. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| /haiku/headers/private/app/ | ||
| H A D | LaunchRoster.h | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| /haiku/src/kits/app/ | ||
| H A D | LaunchRoster.cpp | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
| /haiku/src/servers/mount/ | ||
| H A D | AutoMounter.cpp | diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. diff 7cd19b7e Sat Oct 17 06:07:53 MDT 2015 Axel Dörfler <axeld@pinc-software.de> launch_daemon: Implemented sticky events, and registration. * Sticky events are events that keep their signal raised, ie. even if a job is initialized afterwards, it will still be triggered. * Consolidated naming for external events. * Events are now registered once they are actually being used. This allows them to allocate the resources they need to do their thing. |
Completed in 157 milliseconds