Hello community, here is the log from the commit of package libvirt-cim for openSUSE:Factory checked in at 2014-02-26 06:58:31 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/libvirt-cim (Old) and /work/SRC/openSUSE:Factory/.libvirt-cim.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "libvirt-cim" Changes: -------- --- /work/SRC/openSUSE:Factory/libvirt-cim/libvirt-cim.changes 2014-02-25 07:33:29.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.libvirt-cim.new/libvirt-cim.changes 2014-02-26 06:58:31.000000000 +0100 @@ -1,0 +2,5 @@ +Tue Feb 25 12:54:27 UTC 2014 - [email protected] + +- add README.SUSE + +------------------------------------------------------------------- New: ---- README.SUSE ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ libvirt-cim.spec ++++++ --- /var/tmp/diff_new_pack.ofDCWR/_old 2014-02-26 06:58:33.000000000 +0100 +++ /var/tmp/diff_new_pack.ofDCWR/_new 2014-02-26 06:58:33.000000000 +0100 @@ -50,6 +50,7 @@ Summary: CMPI-based CIM provider implementing DMTF SVPC model Source: %{name}-%{version}.tar.bz2 Source1: libvirt-cim-rpmlintrc +Source2: README.SUSE Patch0: provider-reg.patch Patch1: automake.patch BuildRoot: %{_tmppath}/%{name}-%{version}-build @@ -114,6 +115,8 @@ #%{__rm} -f $RPM_BUILD_ROOT%{_datadir}/%{name}/fix_schema.patch mkdir -p $RPM_BUILD_ROOT/%{_sysconfdir}/libvirt/cim +install -m 644 %{S:2} $RPM_BUILD_ROOT%{_docdir}/%{name} + %clean %{__rm} -rf $RPM_BUILD_ROOT # do nothing if not an upgrade, otherwise deregister current providers ++++++ README.SUSE ++++++ tl;dr libvirt-cim providers don't unload. Increase provProcs to 64 in /etc/sfcb/sfcb.cfg The libvirt-cim providers will not unload after use and might prevent the loading of other providers in sfcb. Please edit /etc/sfcb/sfcb.cfg to increase the provProcs to 64. To quote upstream: "the crux lies in the usage of the libcmpiutil DEFAULT_INST_CLEANUP macro which prevents the provider from being unloaded. sfcb doesn't unload providers forcibly by design, so it is not bug. In the long run, it would probably be desirable to allow the unloading of the libvirt-cim providers. For now, the number of processes would need to be increased." -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
