On Fri, Mar 07, 2014 at 01:50:34AM +0100, Thomas Bächler wrote:
> The instance name is never escaped in the udev rule, but unescaped in the
> unit.
> This results in the following error message on Asus boards:
>
> Failed to get backlight or LED device 'backlight:eeepc/wmi': No such file
> or d
On Fri, Mar 07, 2014 at 12:13:39AM +0100, Armin K. wrote:
> On 03/04/2014 04:23 PM, Armin K wrote:
> > It contains hardcoded path to systemd-sysctl executable which
> > is /usr/lib/systemd/systemd-sysctl on latest stable release and
> > as such it will complain at runtime if rootprefix != prefix
>
The instance name is never escaped in the udev rule, but unescaped in the unit.
This results in the following error message on Asus boards:
Failed to get backlight or LED device 'backlight:eeepc/wmi': No such file or
directory
---
units/systemd-backli...@.service.in | 6 +++---
1 file changed,
On Thu, Mar 6, 2014 at 2:57 PM, David Farning wrote:
> Now my philosophical sticking point is how big pid1 should be to do
> what it needs to do. Practically, I am trying to understand where
> those boundaries should be and how to communicate that information.
A large amount of systemd's code doe
On 03/04/2014 04:23 PM, Armin K wrote:
> It contains hardcoded path to systemd-sysctl executable which
> is /usr/lib/systemd/systemd-sysctl on latest stable release and
> as such it will complain at runtime if rootprefix != prefix
> ---
> Makefile.am | 1 -
> 1 file changed, 1 deletion(-)
>
> dif
Sorry if it seems that I was criticizing systemd's use of ideas from
other projects. That was not my intent. I respect the reuse of proven
good ideas. I am trying to get my mind wrapped around how all the the
ideas came together.
Now my philosophical sticking point is how big pid1 should be to do
On Mon, Mar 3, 2014 at 5:47 PM, David Farning wrote:
> Several of the ground breaking ideas in systemd seem to come directly from
> launchd.
systemd makes no claim to be original or ground-breaking with many of
its ideas. As you mention, some come from launchd. Others come from
Solaris service ma
Applied. Thanks!
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Thu, 06.03.14 16:55, Dariusz Michaluk (d.micha...@samsung.com) wrote:
>
> On 05.03.2014 19:16, Lennart Poettering wrote:
> >nspawn and libvirt-lxc mostly follow the same code paths and register
> >via machined... So it's weird that different things happen. Somehow the
> >systemd instance insid
On 05.03.2014 19:16, Lennart Poettering wrote:
nspawn and libvirt-lxc mostly follow the same code paths and register
via machined... So it's weird that different things happen. Somehow the
systemd instance inside the container must be confused about the cgroup
it is running in...
Next few cents
From: Harald Hoyer
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 systemd serial
On Thu, 06.03.14 09:12, har...@redhat.com (har...@redhat.com) wrote:
> From: Harald Hoyer
>
> 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
Hi
Very sorry. I sent not complete email. Bellow I attached all details
for nspawn case:
++
+++ Guset
++
tizen login: root
Welcome to Tizen
root:~> systemctl show
...
DefaultStandardError=journal
RuntimeWatchdogUSec=0
ShutdownWatchdogUSec=10min
ControlGroup=/machine.sli
On Thu, Mar 06, 2014 at 09:12:58AM +0100, har...@redhat.com wrote:
> From: Harald Hoyer
>
> 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 sys
Hi
In previous mail I putted case for libvirt. In case of nspawn
everything works fine (see details below):
+++ Guest
Jacek Pielaszkiewicz
Samsung R&D Institute Poland
Samsung Electronics
Email: j.pielasz...@samsung.com
> -Original Message-
>
Hi
+++ Host
sh-4.2# systemctl --version
systemd 210
+PAM -LIBWRAP -AUDIT -SELINUX +IMA -SYSVINIT -LIBCRYPTSETUP +GCRYPT +ACL +XZ
-SECCOMP -APPARMOR
sh-4.2#
sh-4.2# systemctl show
Version=210
Features=+PAM -LIBWRAP -AUDIT -SELINUX +IMA -SYSVI
2014-03-06 0:23 GMT+01:00 Usman :
> 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?
Shell probably not, but you should be able to quickly hack together
somethin
On 05.03.2014 19:16, Lennart Poettering wrote:
Oh, yuck! THis is weird. Can you get a gdb backtrac and/or valgrind run
for this? Can't reproduce this here...
(gdb) run show
Starting program: /usr/bin/systemctl show
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/
Use the same formatting as the systemd-analyze man page, so that man shows a
space.
---
man/systemd-bootchart.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man/systemd-bootchart.xml b/man/systemd-bootchart.xml
index d0adaad..1715d5d 100644
--- a/man/systemd-bootchart
Hi!
Based on SYSTEMD_READY definition, I think we should also mark loop
devices with no file attached as not ready:
rules: mark loop device as SYSTEMD_READY=0 if no file is attached
Check existence of loop/backing_file in sysfs and mark loop
devices with SYSTEMD_READY if missing. Suc
From: Harald Hoyer
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 systemd se
From: Harald Hoyer
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 | 22 +++---
src/shared/util.h | 2 ++
2 files changed, 17 insertions(+), 7 deletions(-)
diff --git a
From: Harald Hoyer
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 systemd serial
23 matches
Mail list logo
