On Mon, 08.10.12 15:36, Allmeroth, Robert ([email protected]) wrote:
> 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
On Tue, 09.10.12 14:55, Allmeroth, Robert ([email protected]) wrote:
heya,
> If I do the modprobe on console it's much faster than from within systemd.
> The measurements show that the call to
> int kmod_setup(void) {
> ...
> return wait_for_terminate_and_warn(cmdline[0], pid);
> }
Von: Kay Sievers [mailto:[email protected]]
Gesendet: Montag, 8. Oktober 2012 21:21
An: Allmeroth, Robert
Cc: [email protected]
Betreff: Re: [systemd-devel] startup performance
On Mon, Oct 8, 2012 at 3:36 PM, Allmeroth, Robert
wrote:
> While playing around with systemd and
On Mon, Oct 8, 2012 at 3:36 PM, Allmeroth, Robert
wrote:
> 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",
>
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
