[systemd-devel] Process ordering within a 'dependency level'

2014-03-07 Thread Allmeroth, Robert
Hi, I tried to optimize my embedded configuration but I stumbled over the following problem: Let's assume systemd identified 10 processes on 'dependency level 0'. They all can/should be started first/immediately. Since they cannot be started at the same time - they start sequential with some l

[systemd-devel] threads and cgroups

2014-02-12 Thread Allmeroth, Robert
Hi, I read a lot about the new cgroup concept of the kernel/systemd. I understand the logic behind it and why systemd wants to be the MCP of it. But I miss information how threads are handled. Example: Due to performance reasons we arrange components with various profiles into one executable. As

[systemd-devel] Undefined reference efi_loader_get_boot_usec

2014-02-11 Thread Allmeroth, Robert
Hi, While crosscompiling to an embedded system I got the following error: systemd-208/.libs/libudev.so: undefined reference to `efi_loader_get_boot_usec' I helped myself to #ifdef the body of boot_timestamps() in shared/boot_timestamp.c Best regards Robert Configure: systemd 208

[systemd-devel] Suggestion on StartLimitAction=

2013-02-01 Thread Allmeroth, Robert
Hello, On embedded systems it is sometimes not very useful to call shutdown scripts or reboot(2) in case of a watchdog failure / failed service (re)starting, e.g. FS/Flash corruption, FS driver failure, special HW init failure - Typically important file systems are read-only on embedded systems

[systemd-devel] watchdog chain

2012-12-18 Thread Allmeroth, Robert
Hello, Is it possible to start systemd as a watchdog client? Example: A first systemd starts a second systemd with WATCHDOG_USEC= set. Will the second one send heartbeats to the first one? If yes - will systemd also do that if it's forced to '--system' mode (even if it's not PID1)? Best regard

Re: [systemd-devel] startup performance

2012-10-09 Thread Allmeroth, Robert
44 [4.99] <30>systemd[1]: TIME: after exec_spawn: usec: 4990072 [5.86] NET: Registered protocol family 10 [5.91] <31>systemd[1]: /sbin/modprobe succeeded. [5.91] <30>systemd[1]: TIME: after kmod setup: usec: 5918865 -Ursprüngliche Nachricht-

[systemd-devel] startup performance

2012-10-08 Thread Allmeroth, Robert
Hello, While playing around with systemd and our automotive setup we found that systemd checks some kernel features at startup (from systemd 33). static const char * const kmod_table[] = { "autofs4", "/sys/class/misc/autofs", "ipv6","/sys/module/ipv6", "unix","/pro