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