[opensuse-factory] systemd 208 for 13.1
Hi, 13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo. So if you see problems, please report them as early as possible. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 23/10/13 10:52, Stephan Kulow escribió:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
Greetings, Stephan
Already did that on my two home boxes, no problems found. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-10-23 16:33, Cristian Rodríguez wrote:
El 23/10/13 10:52, Stephan Kulow escribió:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
Already did that on my two home boxes, no problems found.
Reboot aparently crashed after the update. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On 10/23/2013 09:52 AM, Stephan Kulow wrote:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
Greetings, Stephan
No problems booting with 208 on a Dell netbook rng-tools.service fails to start but that is probably not related to the systemd version Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 23/10/13 11:48, Robert Schweikert escribió:
rng-tools.service fails to start but that is probably not related to the systemd version
I modified this package the last time.. IIRC, can you tell what is the exact message and what your hardware RNG is.. ? -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/23/2013 12:48 PM, Cristian Rodríguez wrote:
El 23/10/13 11:48, Robert Schweikert escribió:
rng-tools.service fails to start but that is probably not related to the systemd version
I modified this package the last time.. IIRC, can you tell what is the exact message and what your hardware RNG is.. ?
rng-tools.service - Start the rngd daemon Loaded: loaded (/usr/lib/systemd/system/rng-tools.service; enabled) Active: failed (Result: exit-code) since Wed 2013-10-23 10:41:52 EDT; 2h 22min ago Process: 557 ExecStart=/usr/sbin/rngd --foreground --fill-watermark=90% (code=exited, status=1/FAILURE) Main PID: 557 (code=exited, status=1/FAILURE) CGroup: /system.slice/rng-tools.service Oct 23 10:41:52 warlock systemd[1]: Starting Start the rngd daemon... Oct 23 10:41:52 warlock systemd[1]: Started Start the rngd daemon. Oct 23 10:41:52 warlock systemd[1]: rng-tools.service: main process exited, code=exited, status=1/FAILURE Oct 23 10:41:52 warlock systemd[1]: Unit rng-tools.service entered failed state. Info from syslog: 2013-10-23T13:04:56.382872-04:00 warlock systemd[1]: Starting Start the rngd daemon... 2013-10-23T13:04:56.390550-04:00 warlock systemd[1]: Started Start the rngd daemon. 2013-10-23T13:04:56.392911-04:00 warlock rngd[2375]: Unable to open file: /dev/tpm0 2013-10-23T13:04:56.395189-04:00 warlock rngd[2375]: can't open any entropy source 2013-10-23T13:04:56.398730-04:00 warlock rngd[2375]: Maybe RNG device modules are not loaded 2013-10-23T13:04:56.405432-04:00 warlock systemd[1]: rng-tools.service: main process exited, code=exited, status=1/FAILURE 2013-10-23T13:04:56.411369-04:00 warlock systemd[1]: Unit rng-tools.service ente This is an x86 (Atom) Netbook, there is no hardware RNG. Thus I have to wonder where it was decided that rngd should even be enabled???? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 23/10/13 14:12, Robert Schweikert escribió:
On 10/23/2013 12:48 PM, Cristian Rodríguez wrote:
El 23/10/13 11:48, Robert Schweikert escribió:
rng-tools.service fails to start but that is probably not related to the systemd version
I modified this package the last time.. IIRC, can you tell what is the exact message and what your hardware RNG is.. ?
rng-tools.service - Start the rngd daemon Loaded: loaded (/usr/lib/systemd/system/rng-tools.service; enabled) Active: failed (Result: exit-code) since Wed 2013-10-23 10:41:52 EDT; 2h 22min ago Process: 557 ExecStart=/usr/sbin/rngd --foreground --fill-watermark=90% (code=exited, status=1/FAILURE) Main PID: 557 (code=exited, status=1/FAILURE) CGroup: /system.slice/rng-tools.service
Oct 23 10:41:52 warlock systemd[1]: Starting Start the rngd daemon... Oct 23 10:41:52 warlock systemd[1]: Started Start the rngd daemon. Oct 23 10:41:52 warlock systemd[1]: rng-tools.service: main process exited, code=exited, status=1/FAILURE Oct 23 10:41:52 warlock systemd[1]: Unit rng-tools.service entered failed state.
Info from syslog: 2013-10-23T13:04:56.382872-04:00 warlock systemd[1]: Starting Start the rngd daemon... 2013-10-23T13:04:56.390550-04:00 warlock systemd[1]: Started Start the rngd daemon. 2013-10-23T13:04:56.392911-04:00 warlock rngd[2375]: Unable to open file: /dev/tpm0 2013-10-23T13:04:56.395189-04:00 warlock rngd[2375]: can't open any entropy source 2013-10-23T13:04:56.398730-04:00 warlock rngd[2375]: Maybe RNG device modules are not loaded 2013-10-23T13:04:56.405432-04:00 warlock systemd[1]: rng-tools.service: main process exited, code=exited, status=1/FAILURE 2013-10-23T13:04:56.411369-04:00 warlock systemd[1]: Unit rng-tools.service ente
This is an x86 (Atom) Netbook, there is no hardware RNG. Thus I have to wonder where it was decided that rngd should even be enabled????
I do not know what "enabled" it, whatever it did, is wrong, since nowadays rng-tools will come up automatically when a hwrng device is registered or when the user has manually configured/enabled the daemon explicitly. I suggest you remove the package and install haveged in that machine. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/23/2013 01:39 PM, Cristian Rodríguez wrote:
El 23/10/13 14:12, Robert Schweikert escribió:
On 10/23/2013 12:48 PM, Cristian Rodríguez wrote:
El 23/10/13 11:48, Robert Schweikert escribió:
rng-tools.service fails to start but that is probably not related to the systemd version
I modified this package the last time.. IIRC, can you tell what is the exact message and what your hardware RNG is.. ?
rng-tools.service - Start the rngd daemon Loaded: loaded (/usr/lib/systemd/system/rng-tools.service; enabled) Active: failed (Result: exit-code) since Wed 2013-10-23 10:41:52 EDT; 2h 22min ago Process: 557 ExecStart=/usr/sbin/rngd --foreground --fill-watermark=90% (code=exited, status=1/FAILURE) Main PID: 557 (code=exited, status=1/FAILURE) CGroup: /system.slice/rng-tools.service
Oct 23 10:41:52 warlock systemd[1]: Starting Start the rngd daemon... Oct 23 10:41:52 warlock systemd[1]: Started Start the rngd daemon. Oct 23 10:41:52 warlock systemd[1]: rng-tools.service: main process exited, code=exited, status=1/FAILURE Oct 23 10:41:52 warlock systemd[1]: Unit rng-tools.service entered failed state.
Info from syslog: 2013-10-23T13:04:56.382872-04:00 warlock systemd[1]: Starting Start the rngd daemon... 2013-10-23T13:04:56.390550-04:00 warlock systemd[1]: Started Start the rngd daemon. 2013-10-23T13:04:56.392911-04:00 warlock rngd[2375]: Unable to open file: /dev/tpm0 2013-10-23T13:04:56.395189-04:00 warlock rngd[2375]: can't open any entropy source 2013-10-23T13:04:56.398730-04:00 warlock rngd[2375]: Maybe RNG device modules are not loaded 2013-10-23T13:04:56.405432-04:00 warlock systemd[1]: rng-tools.service: main process exited, code=exited, status=1/FAILURE 2013-10-23T13:04:56.411369-04:00 warlock systemd[1]: Unit rng-tools.service ente
This is an x86 (Atom) Netbook, there is no hardware RNG. Thus I have to wonder where it was decided that rngd should even be enabled????
I do not know what "enabled" it, whatever it did, is wrong, since nowadays rng-tools will come up automatically when a hwrng device is registered or when the user has manually configured/enabled the daemon explicitly.
I suggest you remove the package and install haveged in that machine.
That's already installed. Removed rng-tools Thanks, Robert
-- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Wed, 23 Oct 2013 15:52:25 +0200 schrieb Stephan Kulow <coolo@suse.de>:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
Greetings, Stephan
Hi, update done (with zypper up), no problems during or after the upgrade. Regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, October 23, 2013 03:52:25 PM Stephan Kulow wrote:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
Greetings, Stephan
Upgraded and reboot without issues on LVM with Home encrypted. I would say it improved the startup and poweroff times by reducing both. Regards, -- Ricardo Chung | Panama Member openSUSE Projects -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/23/2013 08:52 AM, Stephan Kulow wrote:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
The 355 upgrades surprised me, but all seems OK. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 23 October 2013, Stephan Kulow wrote:
Hi,
13.1 repo has systemd 207, but Frederic wants to upgrade to 208, so we put it up for testing in the update repo.
So if you see problems, please report them as early as possible.
How to restart the user instances of systemd? I've tried rudi@tenfore:~> systemctl --user daemon-reexec Failed to get D-Bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 rudi@tenfore:~> who root tty1 2013-10-10 21:22 rudi :0 2013-10-10 21:23 (console) sheyma :1 2013-10-16 12:10 (localhost) root pts/2 2013-10-24 12:08 (2a01:170:xxxx::xxxx) rudi@tenfore:~> export DISPLAY=:0 rudi@tenfore:~> systemctl --user daemon-reexec Failed to issue method call: Process /bin/false exited with status 1 What is the user instance good for at all? I does not seem to work: rudi@tenfore:~> systemctl status --user Failed to issue method call: Process /bin/false exited with status 1 cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Thu, 24 Oct 2013 12:24:13 +0200 Ruediger Meier <sweet_f_a@gmx.de> пишет:
What is the user instance good for at all?
At the moment it does not really do anything useful. There are several attempts with different level of success, you can check systemd-devel archives. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 24 October 2013, Andrey Borzenkov wrote:
В Thu, 24 Oct 2013 12:24:13 +0200
Ruediger Meier <sweet_f_a@gmx.de> пишет:
What is the user instance good for at all?
At the moment it does not really do anything useful.
So why it is running then by default? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Andrey Borzenkov -
Carlos E. R. -
Cristian Rodríguez -
dieter -
Larry Finger -
Rick Chung -
Robert Schweikert -
Ruediger Meier -
Stephan Kulow