Hi,
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: den 4 mars 2014 22:00
To: Umut Tezduyar
Cc: Umut Tezduyar Lindskog; systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] StartupFinished signal is not sent on 210
On Tue, 04.03.14
Similar to CPUShares= and BlockIOWeight= respectively. However only
assign the specified weight during startup. Each control group
attribute is re-assigned as weight by CPUShares=weight and
BlockIOWeight=weight after startup. If not CPUShares= or
BlockIOWeight= be specified, then the attribute is
On Wed 05 Mar 2014 04:47:13 Lennart Poettering wrote:
On Tue, 25.02.14 17:59, Barry Scott (barry.sc...@onelan.co.uk) wrote:
Which should make them available via the bus for transient units. If you
need other props like this, just let me know and I'll add them too...
I just tried to set
On 04.03.2014 21:10, Lennart Poettering wrote:
OK, this looks wrong, the machine slice appears to have been used twice
in the cgroup path.
Can you try this with 210 in the container, and then run systemctl
show and report the value of the ControlGroup property, please?
If you boot this up
Hello Everyone,
May any one let me know how to customize systemd to fast boot so that
systemd initialization can be done in parallel on the multiple (like - four
) core to speed up boot process.
Thanks in advance.
Regards,
Manmohan
___
systemd-devel
Hi Mark,
On Wed, Mar 5, 2014 at 1:41 AM, Mark Oteiza mvote...@udel.edu wrote:
networkd: Restore logic for enslaving to a master bonding interface.
Applied. Thanks!
Bonding support seems to have been removed right after being added,
between 52433f6 (22 Jan) and 54abf46 (25 Jan).
This really makes no sense to me at all, i don't grok a word of what you
are writing here.
The term host refers the system the containers run on, usually...
Your remark here is relevant. After googling a little bit Linux
container, many wiki/articles refer to the HOST as opposed to the
On Wed, 05.03.14 09:07, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote:
Of course, I must admit it is less than ideal that with logind around you
might
be able to get away with never calling it... That certainly hides bugs...
We don't have logind and we certainly weren't calling
Hi,
I want journald to send emergency messages to logged-in users, and I think
this is a general enough way to do it.
These patches adds two new options for journald.conf:
* ForwardToWall (default no)
* MaxLevelWall (default emerg)
When ForwardToWall is yes, journald forwards all log messages
utmp_wall() now takes an optional argument 'username_override' which
allows the caller to override the username shown on wall messages.
journald will use this to inform users that its wall messages comes from
'systemd-journald'.
---
src/shared/utmp-wtmp.c | 12
This will let journald forward logs as messages sent to all logged in
users (like wall).
Two options are added:
* ForwardToWall (default no)
* MaxLevelWall (default emerg)
'ForwardToWall' is overridable by kernel command line option
'systemd.journald.forward_to_wall'.
This can be used to
From: Harald Hoyer har...@redhat.com
If systemctl switch-root is called with a specific INIT or
/proc/cmdline contains init=, then systemd would not serialize
itsself.
Let systemctl check, if the new init is in the standard systemd
installation path and if so, clear the INIT parameter,
to
From: Harald Hoyer har...@redhat.com
files_same() returns
1, if the files are the same
0, if the files have different inode/dev numbers
errno, for any stat error
---
src/shared/util.c | 20 +---
src/shared/util.h | 2 ++
2 files changed, 15 insertions(+), 7
From: Harald Hoyer har...@redhat.com
If systemctl switch-root is called with a specific INIT or
/proc/cmdline contains init=, then systemd would not serialize
itsself.
Let systemctl check, if the new init is in the standard systemd
installation path and if so, clear the INIT parameter,
to let
Hi,
both patches look useful. Some comments below.
On Wed, Mar 05, 2014 at 01:46:01PM +0100, Sebastian Thorarensen wrote:
utmp_wall() now takes an optional argument 'username_override' which
allows the caller to override the username shown on wall messages.
journald will use this to inform
From: Harald Hoyer har...@redhat.com
If systemctl switch-root is called with a specific INIT or
/proc/cmdline contains init=, then systemd would not serialize
itsself.
Let systemctl check, if the new init is in the standard systemd
installation path and if so, clear the INIT parameter,
to let
On Wed, Mar 05, 2014 at 01:45:51PM +0100, Sebastian Thorarensen wrote:
This will let journald forward logs as messages sent to all logged in
users (like wall).
Two options are added:
* ForwardToWall (default no)
Is there a good reason not to set it to yes by default?
* MaxLevelWall
On Wed, Mar 05, 2014 at 02:37:47PM +0100, har...@redhat.com wrote:
From: Harald Hoyer har...@redhat.com
If systemctl switch-root is called with a specific INIT or
/proc/cmdline contains init=, then systemd would not serialize
itsself.
Let systemctl check, if the new init is in the
On 03/05/2014 02:55 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Mar 05, 2014 at 02:37:47PM +0100, har...@redhat.com wrote:
From: Harald Hoyer har...@redhat.com
If systemctl switch-root is called with a specific INIT or
/proc/cmdline contains init=, then systemd would not serialize
Hi Guys,
Probably this question has been asked before and it might be a DBus list
question rather than systemd but just asking anyway, so please pardon my
ignorance. I am using dbus-send to get some properties out of systemd dbus
messages when an application dies. The thing is that I need to
On Wed, 05.03.14 08:42, Usman (deser...@yahoo.com) wrote:
Hi Guys,
Probably this question has been asked before and it might be a DBus
list question rather than systemd but just asking anyway, so please
pardon my ignorance. I am using dbus-send to get some properties out
of systemd dbus
systemd-backlight saves backlight levels on shutdown, and restores them
on startup. However, on some systems, backlight level 0 actually turns
the backlight *off*; this can potentially make the system unusable.
Complicating matters, on most systems, nothing pays attention to the
brightness
Hi
On Wed, Mar 5, 2014 at 6:46 PM, Josh Triplett j...@joshtriplett.org wrote:
systemd-backlight saves backlight levels on shutdown, and restores them
on startup. However, on some systems, backlight level 0 actually turns
the backlight *off*; this can potentially make the system unusable.
On Wed, 05.03.14 09:46, Josh Triplett (j...@joshtriplett.org) wrote:
systemd-backlight saves backlight levels on shutdown, and restores them
on startup. However, on some systems, backlight level 0 actually turns
the backlight *off*; this can potentially make the system unusable.
Complicating
On Wed, 05.03.14 11:38, Dariusz Michaluk (d.micha...@samsung.com) wrote:
I can't report the value of the ControlGroup property, I get this:
# systemctl show
Segmentation fault
Oh, yuck! THis is weird. Can you get a gdb backtrac and/or valgrind run
for this? Can't reproduce this here...
On Wed, 05.03.14 14:37, har...@redhat.com (har...@redhat.com) wrote:
-return
-a.st_dev != b.st_dev ||
-a.st_ino != b.st_ino;
+return (a.st_dev == b.st_dev a.st_ino == b.st_ino);
No need for the extra ()...
+}
+
+int running_in_chroot(void)
On Wed, 05.03.14 14:37, har...@redhat.com (har...@redhat.com) wrote:
From: Harald Hoyer har...@redhat.com
If systemctl switch-root is called with a specific INIT or
/proc/cmdline contains init=, then systemd would not serialize
itsself.
Let systemctl check, if the new init is in the
When is startup considered over? I'd like if it meant before the
WantedBy unit was started so this value still has use for arbitrary
startup.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Manmohan Singh manmohan.mani2...@gmail.com schrieb:
Hello Everyone,
May any one let me know how to customize systemd to fast boot so that
systemd initialization can be done in parallel on the multiple (like -
four ) core to speed up boot process.
Systemd already does this by design
On Wed, Mar 05, 2014 at 06:59:27PM +0100, David Herrmann wrote:
On Wed, Mar 5, 2014 at 6:46 PM, Josh Triplett j...@joshtriplett.org wrote:
systemd-backlight saves backlight levels on shutdown, and restores them
on startup. However, on some systems, backlight level 0 actually turns
the
On Wed, Mar 05, 2014 at 07:10:51PM +0100, Lennart Poettering wrote:
On Wed, 05.03.14 09:46, Josh Triplett (j...@joshtriplett.org) wrote:
systemd-backlight saves backlight levels on shutdown, and restores them
on startup. However, on some systems, backlight level 0 actually turns
the
---
TODO|1 -
man/systemd.network.xml |9 +
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/TODO b/TODO
index fd75eab..dbfe48e 100644
--- a/TODO
+++ b/TODO
@@ -670,7 +670,6 @@ Features:
- add proper initrd support (in particular generate
I can reproduce similar behaviour on Fedora 21. I used Linux 3.14.0-0.rc5,
systemd 210 on host and guest machine, libvirtd 1.2.2.
See this yesterday thread
Network unreachable in container
and Lennart comment : What is Host ? What is guest ??
___
Applied. Thanks!
-t
On Wed, Mar 5, 2014 at 8:51 PM, Umut Tezduyar Lindskog
umut.tezdu...@axis.com wrote:
---
TODO|1 -
man/systemd.network.xml |9 +
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/TODO b/TODO
index fd75eab..dbfe48e 100644
Hi
On Wed, Mar 5, 2014 at 8:31 PM, Josh Triplett j...@joshtriplett.org wrote:
On Wed, Mar 05, 2014 at 07:10:51PM +0100, Lennart Poettering wrote:
On Wed, 05.03.14 09:46, Josh Triplett (j...@joshtriplett.org) wrote:
systemd-backlight saves backlight levels on shutdown, and restores them
on
On Wed, Mar 05, 2014 at 10:21:17PM +0100, David Herrmann wrote:
On Wed, Mar 5, 2014 at 8:31 PM, Josh Triplett j...@joshtriplett.org wrote:
On Wed, Mar 05, 2014 at 07:10:51PM +0100, Lennart Poettering wrote:
On Wed, 05.03.14 09:46, Josh Triplett (j...@joshtriplett.org) wrote:
From: Thomas Hindoe Paaboel Andersen pho...@gmail.com
--system
-H --host
-M --machine
--service-type (options: simple forking oneshot dbus notify idle)
--uid
--gid
--nice
--setenv
-p --property (options read from bus_append_unit_property_assignment)
---
shell-completion/bash/systemd-run | 39
Thanks Lennart. Is there a way I can do it from shell rather than writing C or
Java code? I just want to quickly verify that the messages I get once Unit
state changes. Any example?
Thanks.
On Wednesday, March 5, 2014 2:22 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed,
On Wed, 5 Mar 2014, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Mar 05, 2014 at 01:45:51PM +0100, Sebastian Thorarensen wrote:
This will let journald forward logs as messages sent to all logged in
users (like wall).
Two options are added:
* ForwardToWall (default no)
Is there a good
Thanks for the review. Here is an updated version of the patches.
Changes since v1:
* ForwardToWall is now enabled by default
* Fixed errors in journald-wall.c (a colon was printed even when there
was no identifier and pid)
* Coding style fixes
Sebastian Thorarensen (2):
utmp-wtmp: allow
utmp_wall() now takes an optional argument 'username_override' which
allows the caller to override the username shown on wall messages.
journald will use this to inform users that its wall messages comes from
'systemd-journald'.
---
src/shared/utmp-wtmp.c | 12
This will let journald forward logs as messages sent to all logged in
users (like wall).
Two options are added:
* ForwardToWall (default yes)
* MaxLevelWall (default emerg)
'ForwardToWall' is overridable by kernel command line option
'systemd.journald.forward_to_wall'.
This is used to emulate
42 matches
Mail list logo
