Hello community,
here is the log from the commit of package yast2-cluster for openSUSE:Factory
checked in at 2014-09-03 12:50:37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/yast2-cluster (Old)
and /work/SRC/openSUSE:Factory/.yast2-cluster.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "yast2-cluster"
Changes:
--------
--- /work/SRC/openSUSE:Factory/yast2-cluster/yast2-cluster.changes
2014-07-16 16:22:23.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.yast2-cluster.new/yast2-cluster.changes
2014-09-03 12:50:42.000000000 +0200
@@ -1,0 +2,6 @@
+Wed Sep 3 02:45:51 UTC 2014 - nw...@suse.com
+
+- BNC#787196. Change wrong unit names like mb to Mb, ghz to GHz.
+- Version 3.1.13
+
+-------------------------------------------------------------------
Old:
----
yast2-cluster-3.1.12.tar.bz2
New:
----
yast2-cluster-3.1.13.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-cluster.spec ++++++
--- /var/tmp/diff_new_pack.9ocrAO/_old 2014-09-03 12:50:43.000000000 +0200
+++ /var/tmp/diff_new_pack.9ocrAO/_new 2014-09-03 12:50:43.000000000 +0200
@@ -18,7 +18,7 @@
Name: yast2-cluster
%define _fwdefdir /etc/sysconfig/SuSEfirewall2.d/services
-Version: 3.1.12
+Version: 3.1.13
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
++++++ yast2-cluster-3.1.12.tar.bz2 -> yast2-cluster-3.1.13.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-cluster-3.1.12/package/yast2-cluster.changes
new/yast2-cluster-3.1.13/package/yast2-cluster.changes
--- old/yast2-cluster-3.1.12/package/yast2-cluster.changes 2014-07-16
12:28:50.000000000 +0200
+++ new/yast2-cluster-3.1.13/package/yast2-cluster.changes 2014-09-03
04:52:07.000000000 +0200
@@ -1,4 +1,10 @@
-------------------------------------------------------------------
+Wed Sep 3 02:45:51 UTC 2014 - nw...@suse.com
+
+- BNC#787196. Change wrong unit names like mb to Mb, ghz to GHz.
+- Version 3.1.13
+
+-------------------------------------------------------------------
Tue Jul 15 10:17:03 UTC 2014 - nw...@suse.com
- BNC#885018. Change "two_node" to "0" when using default value.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-cluster-3.1.12/package/yast2-cluster.spec
new/yast2-cluster-3.1.13/package/yast2-cluster.spec
--- old/yast2-cluster-3.1.12/package/yast2-cluster.spec 2014-07-16
12:28:50.000000000 +0200
+++ new/yast2-cluster-3.1.13/package/yast2-cluster.spec 2014-09-03
04:52:07.000000000 +0200
@@ -18,7 +18,7 @@
Name: yast2-cluster
%define _fwdefdir /etc/sysconfig/SuSEfirewall2.d/services
-Version: 3.1.12
+Version: 3.1.13
Release: 0
BuildRoot: %{_tmppath}/%{name}-%{version}-build
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/yast2-cluster-3.1.12/src/include/cluster/helps.rb
new/yast2-cluster-3.1.13/src/include/cluster/helps.rb
--- old/yast2-cluster-3.1.12/src/include/cluster/helps.rb 2014-07-07
09:52:32.000000000 +0200
+++ new/yast2-cluster-3.1.13/src/include/cluster/helps.rb 2014-09-03
04:52:07.000000000 +0200
@@ -45,7 +45,7 @@
"security" => _(
"\n" +
"<p><b><big>Threads</big></b><br>This directive controls how many
threads are used to encrypt and send multicast messages. If secauth is off,
the protocol will never use threaded sending. If secauth is on, this
directive allows systems to be configured to use multiple threads to
encrypt and send multicast messages. A thread directive of 0 indicates that
no threaded send should be used. This mode offers best performance for non-SMP
systems. The default is 0. <br></p>\n" +
- "<p><b><big>Enable Security Auth</big></b><br>This specifies
that HMAC/SHA1 authentication should be used to authenticate all messages. It
further specifies that all data should be encrypted with the sober128
encryption algorithm to protect data from eavesdropping. Enabling this option
adds a 36 byte header to every message sent by totem which reduces total
throughput. Encryption and authentication consume 75% of CPU cycles in aisexec
as measured with gprof when enabled. For 100mbit networks with 1500 MTU
frame transmissions: A throughput of 9mb/sec is possible with 100% cpu
utilization when this option is enabled on 3ghz cpus. A throughput of
10mb/sec is possible wth 20% cpu utilization when this option is disabled on
3ghz cpus. For gig-e networks with large frame transmissions: A throughput of
20mb/sec is possible when this option is enabled on 3ghz cpus. A
throughput of 60mb/sec is possible when this option is disabled on 3ghz cpus.
The default is on. <br></p>\n"
+ "<p><b><big>Enable Security Auth</big></b><br>This specifies
that HMAC/SHA1 authentication should be used to authenticate all messages. It
further specifies that all data should be encrypted with the sober128
encryption algorithm to protect data from eavesdropping. Enabling this option
adds a 36 byte header to every message sent by totem which reduces total
throughput. Encryption and authentication consume 75% of CPU cycles in aisexec
as measured with gprof when enabled. For 100Mbit networks with 1500 MTU
frame transmissions: A throughput of 9Mb/s is possible with 100% cpu
utilization when this option is enabled on 3GHz cpus. A throughput of 10Mb/s
is possible wth 20% cpu utilization when this option is disabled on 3GHz cpus.
For gig-e networks with large frame transmissions: A throughput of 20Mb/s is
possible when this option is enabled on 3GHz cpus. A throughput of
60Mb/s is possible when this option is disabled on 3GHz cpus. The default is
on. <br></p>\n"
),
"service" => _(
"\n" +
--
To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org
For additional commands, e-mail: opensuse-commit+h...@opensuse.org
