>>But doesn't executing the systemctl disable command not just removes the >>link from /etc/systemd/system/<targetname>/ ?
oh yes, you are right #systemctl disable watchdog-mux.socket Removed symlink /etc/systemd/system/sockets.target.wants/watchdog-mux.socket. so, in the postinst rm -f /etc/systemd/system/sockets.target.wants/watchdog-mux.socket it should work. >>inc combination with the >> >>systemctl daemon-reload >> >>that should be enough. >> >>Reboot should help here? yes, maybe. I will do tests on my side to see. ----- Mail original ----- De: "Thomas Lamprecht" <[email protected]> À: "pve-devel" <[email protected]> Envoyé: Lundi 25 Janvier 2016 07:41:32 Objet: Re: [pve-devel] watchdog-mux.socket has been removed, but not disabled On 01/25/2016 07:03 AM, Alexandre DERUMIER wrote: > Hi, > > since this commit > https://git.proxmox.com/?p=pve-ha-manager.git;a=commit;h=f8a3fc80af299e613c21c9b67e29aee8cc807018 > > > has been removed, > > but for existing config, the service is not disabled (only the unit file is > removed) > > 2 users in the forum > https://forum.proxmox.com/threads/4-1-ha-software-watchdog-reset-does-not-work.25474/#post-128996 > > > have reported warnings messages : > > systemd[1]: Cannot add dependency job for unit watchdog-mux.socket, ignoring: > Unit watchdog-mux.socket failed to load: No such file or directory > > > > I think the postinst script should do a "systemctl disable > watchdog-mux.socket" before remove the unit file. But doesn't executing the systemctl disable command not just removes the link from /etc/systemd/system/<targetname>/ ? the man page says also so: > disable NAME > Disables one or more units. This removes all symlinks to the specified > unit files from the unit configuration directory, and hence undoes the > changes made by enable. Note however that this removes > all symlinks to the unit files (i.e. including manual additions), not > just those actually created by enable. This call implicitly reloads > the systemd daemon configuration after completing the > disabling of the units. Note that this command does not implicitly > stop the units that are being disabled. If this is desired, an > additional stop command should be executed afterwards. inc combination with the systemctl daemon-reload that should be enough. Reboot should help here? > > _______________________________________________ > pve-devel mailing list > [email protected] > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
