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);
> }
Hi list,
The attached patch implements journal integration for the Python
logging framework. Tested on my Arch Linux machine, using Python 2.7
and 3.2, but should be compatible with all versions from 2.5 through
3.3
The logging framework has a mechanism for supplying additional
key-value pairs, b
Add support for scm block devices. Introduced here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=f30664e2
Signed-off-by: Sebastian Ott
---
src/udev/udev-builtin-path_id.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/src/udev/udev-built
AC_CHECK_FUNCS may be successful, even though name_to_handle_at and
'struct file_handle' are not available.
---
"#if !HAVE_DECL_NAME_TO_HANDLE_AT" is the correct test...
configure.ac |7 ---
src/shared/missing.h |2 +-
2 files changed, 5 insertions(+), 4 deletions(-)
diff
Hello,
I did some more time measuring..
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);
}
consumes nearly exactly 1 second.
[4.99] <30>syst
AC_CHECK_FUNCS may be successful, even though name_to_handle_at and
'struct file_handle' are not available.
---
> This really looks like something to fix in libc. I mean, supporting
> libcs with and without this function makes sense, but supporting an
> (obviously broken/contradicting) glibc tha
