-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/16/2012 02:56 PM, Lennart Poettering wrote:
> On Fri, 16.11.12 09:23, Daniel J Walsh ([email protected]) wrote:
>
>> The only problem I see is that now sysV init scripts are firing off
>> within the container. (iSCSI daemon). What can I do to s
On Fri, 16.11.12 09:23, Daniel J Walsh ([email protected]) wrote:
> The only problem I see is that now sysV init scripts are firing off within the
> container. (iSCSI daemon). What can I do to stop this within the container?
Services such as the iscsi daemon which one can sort in the "driver"
ca
On Fri, 16.11.12 09:20, Daniel J Walsh ([email protected]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> ls -l /var/log/journal/
> total 12
> drwxr-xr-x. 2 root root 12288 Nov 16 08:47 1b16d5a8cec649e7ba7d9f9f6ef8f393
> lrwxrwxrwx. 1 root root52 Nov 13 15:24 1f9684eeed2d43d3bf
On Fri, 2012-11-16 at 09:23 -0500, Daniel J Walsh wrote:
> The only problem I see is that now sysV init scripts are firing off within the
> container. (iSCSI daemon). What can I do to stop this within the container?
ConditionVirtualization=!lxc-libvirt ?
On 11/15/12 9:05 PM, Kay Sievers wrote:
You can use systemd to instantiate a service on device discovery (or
run a daemon that listens to events from udev on old init systems).
Check how bluetooth, cups printers, usbmux, ... is handled:
TAG+="systemd",
ENV{SYSTEMD_WANTS}="configure-printer@usb
On Fri, Nov 16, 2012 at 4:49 PM, Peter Lemenkov wrote:
> 2012/11/16 Umut Tezduyar :
>> If firmware file is not found in the file system, udev
>> terminates firmware loading. This is not the case if
>> firmware file exists in the file system but doesn't have
>> any data in it.
>
> This sounds like
Hello All.
2012/11/16 Umut Tezduyar :
> If firmware file is not found in the file system, udev
> terminates firmware loading. This is not the case if
> firmware file exists in the file system but doesn't have
> any data in it.
This sounds like an error which must be fixed somewhere else. Just my
If firmware file is not found in the file system, udev
terminates firmware loading. This is not the case if
firmware file exists in the file system but doesn't have
any data in it.
---
systemd/src/udev/udev-builtin-firmware.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a
On Fri, Nov 16, 2012 at 09:20:52AM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> ls -l /var/log/journal/
> total 12
> drwxr-xr-x. 2 root root 12288 Nov 16 08:47 1b16d5a8cec649e7ba7d9f9f6ef8f393
> lrwxrwxrwx. 1 root root52 Nov 13 15:24 1f9684eeed2d43d3bfee7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The only problem I see is that now sysV init scripts are firing off within the
container. (iSCSI daemon). What can I do to stop this within the container?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with unde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ls -l /var/log/journal/
total 12
drwxr-xr-x. 2 root root 12288 Nov 16 08:47 1b16d5a8cec649e7ba7d9f9f6ef8f393
lrwxrwxrwx. 1 root root52 Nov 13 15:24 1f9684eeed2d43d3bfee702a89f849d6 ->
/var/lib/libvirt/filesystems/apache1/var/log/journal
lrwxrwxrwx
On Tue, Nov 13, 2012 at 12:23 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> I went ahead and merged the patch with some small changes, please have
> a look.
> JournalHandler is already useful right now
Cool, thanks! Agreed, the rest could just be built on top of this code.
On Tue, Nov 13, 2012 at 12:
12 matches
Mail list logo
