tree: 9f4bbaedff8b3114e593c09bbab5a5f4d8dbbcbd [path history] [tgz]
  1. config/
  2. hub/
  3. integration_tests/
  4. meta/
  5. allow_list.cc
  6. allow_list.h
  7. allow_list_unittest.cc
  8. appmgr.cc
  9. appmgr.h
  10. BUILD.gn
  11. cache_control.cc
  12. cache_control.h
  13. component_container.h
  14. component_controller_impl.cc
  15. component_controller_impl.h
  16. component_controller_unittest.cc
  17. component_event_provider_impl.cc
  18. component_event_provider_impl.h
  19. component_event_provider_unittest.cc
  20. component_id_index.cc
  21. component_id_index.h
  22. component_id_index_unittest.cc
  23. constants.h
  24. cpu_watcher.cc
  25. cpu_watcher.h
  26. cpu_watcher_unittest.cc
  27. debug_info_retriever.cc
  28. debug_info_retriever.h
  29. dynamic_library_loader.cc
  30. dynamic_library_loader.h
  31. environment_controller_impl.cc
  32. environment_controller_impl.h
  33. introspector.cc
  34. introspector.h
  35. job_provider_impl.cc
  36. job_provider_impl.h
  37. log_connector_impl.cc
  38. log_connector_impl.h
  39. log_connector_impl_unittest.cc
  40. main.cc
  41. namespace.cc
  42. namespace.h
  43. namespace_builder.cc
  44. namespace_builder.h
  45. namespace_builder_unittest.cc
  46. namespace_unittest.cc
  47. OWNERS
  48. policy_checker.cc
  49. policy_checker.h
  50. policy_checker_unittest.cc
  51. README.md
  52. realm.cc
  53. realm.h
  54. runner_holder.cc
  55. runner_holder.h
  56. scheme_map.cc
  57. scheme_map.config
  58. scheme_map.h
  59. scheme_map_unittest.cc
  60. service_provider_dir_impl.cc
  61. service_provider_dir_impl.h
  62. service_provider_dir_unittest.cc
  63. storage_unittest.cc
  64. storage_watchdog.cc
  65. storage_watchdog.h
  66. storage_watchdog_unittest.cc
  67. system_diagnostics_directory.cc
  68. system_diagnostics_directory.h
  69. test_file.txt
  70. util.cc
  71. util.h
  72. util_unittest.cc
src/sys/appmgr/README.md

appmgr

Reviewed on: 2019-07-22

Appmgr is responsible for launching v1 components and managing the namespaces in which those components run. It is the first process started in the fuchsia job by devmgr.

See:

Building

This project is typically included in Fuchsia builds by default, but it can be added to a build by adding --with //src/sys/appmgr to the fx set invocation.

Running

Appmgr is run on all non-bringup Fuchsia builds. It can be interacted with via the fuchsia.sys FIDL apis.

Testing

Unit tests for appmgr are available in the appmgr_unittests package.

$ fx run-test appmgr_unittests

Integration tests are available in the following packages, and each can be run with fx run-test.

  • appmgr_integration_tests
  • build_info_tests
  • components_binary_tests
  • has_deprecated_shell
  • has_isolated_cache_storage
  • has_isolated_persistent_storage
  • has_isolated_temp
  • has_shell_commands
  • has_system_temp
  • inspect_integration_tests
  • inspect_vmo_integration_tests
  • isolated_persistent_storage
  • multiple_components
  • no_isolated_temp
  • no_persistent_storage
  • no_services
  • no_shell_commands
  • no_shell
  • no_system_temp
  • some_services
  • uses_system_deprecated_data

Source layout

The entrypoint is located in main.cc, with the majority of the implementation living in top-level .cc and .h files, with the exception of the hub implementation which is in hub/. Unit tests are located in _unittest.cc files.

Integration tests are in the integration_tests/ directory.