Re: [PATCH 14/14] Enable systemd socket activation with virtlockd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/07/2011 04:17 PM, Daniel P. Berrange wrote:
  if [ $1 -eq 1 ] ; then
      # Initial installation
+    /bin/systemctl enable virtlockd.service>/dev/null 2>&1 || :
      /bin/systemctl enable libvirtd.service>/dev/null 2>&1 || :
      /bin/systemctl enable cgconfig.service>/dev/null 2>&1 || :
  fi
@@ -914,8 +915,10 @@ fi
  %if %{with_systemd}
  if [ $1 -eq 0 ] ; then
      # Package removal, not upgrade
+    /bin/systemctl --no-reload disable virtlockd.service>  /dev/null 2>&1 || :
      /bin/systemctl --no-reload disable libvirtd.service>  /dev/null 2>&1 || :
      /bin/systemctl stop libvirtd.service>  /dev/null 2>&1 || :
+    /bin/systemctl stop virtlockd.service>  /dev/null 2>&1 || :
  fi

Do you really want to enable the .service by default rather than the .socket? IIUC, in the common case of no autostart guests enabling the .socket will cut on boot-time operations.

systemd is new to me though, so I may well have misunderstood something...

Paolo

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]