First of all, systemctl detects when it is run in a chroot. If so, most of its operations will become NOPs, with the exception of systemctl enable and systemctl disable. If a package installation script hence calls these two commands, services will be enabled in the guest OS. However, should a package installation script include a command like systemctl restart as part of the package upgrade process this will have no effect at all when run in a chroot() environment.
Description
Change systemctl call on command -v systemctl
What
Improve installation on systemd setup
Why ?
RM:3388776
Change type
What kind of change does this PR introduce?
[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Tests
[ ] Other
Check list
[x] Code follows the style de facto guidelines of this project
[ ] Comments have been inserted in hard to understand places
igor-ivanov
commented
1 year ago
See: http://0pointer.de/blog/projects/changing-roots
First of all, systemctl detects when it is run in a chroot. If so, most of its operations will become NOPs, with the exception of systemctl enable and systemctl disable. If a package installation script hence calls these two commands, services will be enabled in the guest OS. However, should a package installation script include a command like systemctl restart as part of the package upgrade process this will have no effect at all when run in a chroot() environment.
Description
Change systemctl call on
command -v systemctlWhat
Improve installation on systemd setup
Why ?
RM:3388776
Change type
What kind of change does this PR introduce?
Check list