mirror of
https://git.proxmox.com/git/pve-manager
synced 2025-08-14 07:03:23 +00:00
57de747b0c
the name 'pve-manager' collides with our pve-manager package name, which - from the user point of view - provides mainly the API and WebUI. An user could thus think that restarting 'pve-manager' would restart the WebUIs server, which is relatable. But, the pve-manager.service does not controls the WebUI or its server but is responsible for starting all guest with 'onboot=1' in their config on system boot and to stop all remaining running guests on system shutdown. Thus rename it to pve-guests and adapt its description. This may not seem as ideal name at first glance, but its better than the current option. Further it leads to log messages like: > Starting PVE guests (Service providing start-on-boot and stop-all-on-shutdown) > [...] > Started PVE guests (Service providing start-on-boot and stop-all-on-shutdown) > [...] > Stopping PVE guests (Service providing start-on-boot and stop-all-on-shutdown) which makes it clearer what happens, or what this service is for. Alias the new service to the old pve-manager.service for legacy reasons. While our services do not depend on it an user could have made an own service which used pve-manager.service as synchronisation point. Linitian then complains about init.d/pve-manager not having a related systemd service file. Instead of renmaning it just drop it. Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> |
||
|---|---|---|
| aplinfo | ||
| bin | ||
| debian | ||
| PVE | ||
| www | ||
| .gitignore | ||
| bridgevlan | ||
| bridgevlanport | ||
| country.pl | ||
| defines.mk | ||
| Makefile | ||
| mtu | ||
| pve-apt.conf | ||
| pve-blacklist.conf | ||
| pve-initramfs.conf | ||
| pve-sources.list | ||
| repoid.pl | ||
| spice-example-sh | ||
| vlan | ||
| vlan-down | ||
| vzdump-hook-script.pl | ||
| vzdump.conf | ||