tree: 332da07f7f6c4b4b8f82a04258036f94cc883eae [path history] [tgz]
  1. BUILD.gn
  2. OWNERS
  3. README.md
  4. allowlist.cc
  5. allowlist.h
  6. allowlist_unittest.cc
  7. appmgr.cc
  8. appmgr.h
  9. cache_control.cc
  10. cache_control.h
  11. component_container.h
  12. component_controller_impl.cc
  13. component_controller_impl.h
  14. component_controller_unittest.cc
  15. debug_info_retriever.cc
  16. debug_info_retriever.h
  17. deprecated_shell_allowlist.txt
  18. dynamic_library_loader.cc
  19. dynamic_library_loader.h
  20. environment_controller_impl.cc
  21. environment_controller_impl.h
  22. global_data_allowlist.txt
  23. hub/
  24. integration_tests/
  25. job_provider_impl.cc
  26. job_provider_impl.h
  27. main.cc
  28. meta/
  29. namespace.cc
  30. namespace.h
  31. namespace_builder.cc
  32. namespace_builder.h
  33. namespace_builder_unittest.cc
  34. namespace_unittest.cc
  35. realm.cc
  36. realm.h
  37. runner_holder.cc
  38. runner_holder.h
  39. scheme_map.cc
  40. scheme_map.config
  41. scheme_map.h
  42. scheme_map_unittest.cc
  43. service_provider_dir_impl.cc
  44. service_provider_dir_impl.h
  45. service_provider_dir_unittest.cc
  46. storage_watchdog.cc
  47. storage_watchdog.h
  48. storage_watchdog_unittest.cc
  49. system_objects_directory.cc
  50. system_objects_directory.h
  51. test_file.txt
  52. util.cc
  53. util.h
  54. 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.