From: Nathaniel Chen
CIPSO is the Common IP Security Option, an IETF standard for setting
security levels for a process sending packets. In Smack kernels,
CIPSO headers are mapped to Smack labels automatically, but can be changed.
This patch writes label/category mappings from /etc/smack/cipso/
Check all errors. Return the first error if looping.
---
Hi Nathaniel,
your patches duplicate the same code paths (within one function!).
Also, if cipsco is not available, a warning would be printed, which
we don't want.
Can you check if the following two replacement patches work for you?
Please m
Hi,
Colin Walters wrote
>> install-directories-hook:
>> $(MKDIR_P) $(addprefix $(DESTDIR),$(INSTALL_DIRS))
>> + $(MKDIR_P) -m 000 $(addprefix $(DESTDIR),$(INACCESSIBLE_DIR))
> Ugh. Can you make this /run/systemd/inaccessible or something, and
> have systemd do this at runtime?
> Havin
On Tue, Mar 12, 2013 at 06:22:57PM +0100, Michal Sekletar wrote:
> ---
> src/systemctl/systemctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.f
On Thu, Feb 14, 2013 at 10:47:32AM +0200, Albert Strasheim wrote:
> Hello all
>
> We have some systems running systemd-37-25.fc16.x86_64.
>
> We have an issue where a timer unit doesn't fire again if its service
> runs for too long.
For the sake of mailing list archives:
this is not fixed yet, bu
'Twas brillig, and Reindl Harald at 13/03/13 17:37 did gyre and gimble:
> Am 13.03.2013 17:44, schrieb Kay Sievers:
>> On Wed, Mar 13, 2013 at 5:30 PM, Kok, Auke-jan H
>> wrote:
>>> On Wednesday, March 13, 2013, Kay Sievers wrote:
On Wed, Mar 13, 2013 at 3:17 PM, Reindl Harald
wrote:
>
Am 13.03.2013 18:45, schrieb Kay Sievers:
> On Wed, Mar 13, 2013 at 6:37 PM, Reindl Harald wrote:
>> Am 13.03.2013 17:44, schrieb Kay Sievers:
>>> On Wed, Mar 13, 2013 at 5:30 PM, Kok, Auke-jan H
>>> wrote:
On Wednesday, March 13, 2013, Kay Sievers wrote:
> On Wed, Mar 13, 2013 at 3:1
On Wed, Mar 13, 2013 at 6:37 PM, Reindl Harald wrote:
> Am 13.03.2013 17:44, schrieb Kay Sievers:
>> On Wed, Mar 13, 2013 at 5:30 PM, Kok, Auke-jan H
>> wrote:
>>> On Wednesday, March 13, 2013, Kay Sievers wrote:
On Wed, Mar 13, 2013 at 3:17 PM, Reindl Harald
wrote:
> so and
Am 13.03.2013 17:44, schrieb Kay Sievers:
> On Wed, Mar 13, 2013 at 5:30 PM, Kok, Auke-jan H
> wrote:
>> On Wednesday, March 13, 2013, Kay Sievers wrote:
>>> On Wed, Mar 13, 2013 at 3:17 PM, Reindl Harald
>>> wrote:
>>>
so and what are you guys saying if i explain you that
i WANT THIS
On Wed, Mar 13, 2013 at 5:30 PM, Kok, Auke-jan H
wrote:
> On Wednesday, March 13, 2013, Kay Sievers wrote:
>> On Wed, Mar 13, 2013 at 3:17 PM, Reindl Harald
>> wrote:
>>
>>> so and what are you guys saying if i explain you that
>>> i WANT THIS MESSAGES bedcause I WANT to SEE
>>> /dev/sda2: clean
On Wednesday, March 13, 2013, Kay Sievers wrote:
> On Wed, Mar 13, 2013 at 3:17 PM, Reindl Harald
wrote:
>
>> so and what are you guys saying if i explain you that
>> i WANT THIS MESSAGES bedcause I WANT to SEE
>> /dev/sda2: clean, 435608/1310720 files
>
> Now, that you ask, I would say: I don't
On Wed, Mar 13, 2013 at 09:22:34AM -0700, Michal Schmidt wrote:
> src/core/manager.c | 28 +++-
> src/core/mount.c | 48 --
> src/core/service.c | 60
> -
> src/core/socket.c |
On Wed, Mar 13, 2013 at 3:17 PM, Reindl Harald wrote:
> so and what are you guys saying if i explain you that
> i WANT THIS MESSAGES bedcause I WANT to SEE
> /dev/sda2: clean, 435608/1310720 files
Now, that you ask, I would say: I don't care. :)
Kay
_
Am 13.03.2013 15:06, schrieb Colin Guthrie:
> 'Twas brillig, and Kay Sievers at 13/03/13 11:50 did gyre and gimble:
>> On Wed, Mar 13, 2013 at 11:29 AM, Colin Guthrie wrote:
>>> As I'm doing some initrd-less experiments of late I'm seeing an ugly
>>> fsck message pop up on boot.
>>>
>>> In syste
'Twas brillig, and Kay Sievers at 13/03/13 11:50 did gyre and gimble:
> On Wed, Mar 13, 2013 at 11:29 AM, Colin Guthrie wrote:
>> As I'm doing some initrd-less experiments of late I'm seeing an ugly
>> fsck message pop up on boot.
>>
>> In systemd-fsck-root.service I see:
>>
>> StandardOutput=jour
2013/3/13 John :
> On 13/03/13 11:58, Kay Sievers wrote:
>>
>> On the host, "newinstance" is not strictly needed, it is useful inside the
>> container though.
>
> How do I make it use newinstance inside the container? is that a lxc config
> or systemd?
lxc does this explicitly during container star
On Wed, Mar 13, 2013 at 1:32 PM, John wrote:
> On 13/03/13 11:58, Kay Sievers wrote:
>>
>> On the host, "newinstance" is not strictly needed, it is useful inside the
>> container though.
>
> How do I make it use newinstance inside the container? is that a lxc config
> or systemd?
It's lxc's prepa
On 13/03/13 11:58, Kay Sievers wrote:
On the host, "newinstance" is not strictly needed, it is useful inside
the container though.
How do I make it use newinstance inside the container? is that a lxc
config or systemd?
___
systemd-devel mailing list
On Wed, Mar 13, 2013 at 11:38 AM, John Lane wrote:
> Good morning, I am trying to get LXC guests working with systemd. I am at
> the point where I can start a container but it is affecting the host. I've
> been discussing over on lxc-users and it's been suggested that systemd may
> be incorrectly
On Wed, Mar 13, 2013 at 11:29 AM, Colin Guthrie wrote:
> As I'm doing some initrd-less experiments of late I'm seeing an ugly
> fsck message pop up on boot.
>
> In systemd-fsck-root.service I see:
>
> StandardOutput=journal+console
>
> which results in:
>
> systemd-fsck[116]: /dev/sda2: clean, 435
Try adding lxc.mount option into container config using following
mount point file:
sysfs sys sysfs ro,defaults 0 0
proc proc proc nodev,noexec,nosuid 0 0
/proc/sys ${rootfs_path}/proc/sys none ro,bind 0 0
2013/3/13 John Lane :
> Good morning, I am trying to get LXC guests working with systemd.
Good morning, I am trying to get LXC guests working with systemd. I am
at the point where I can start a container but it is affecting the host.
I've been discussing over on lxc-users and it's been suggested that
systemd may be incorrectly mounting devpts without the "newinstance"
option. I unde
Hi,
As I'm doing some initrd-less experiments of late I'm seeing an ugly
fsck message pop up on boot.
In systemd-fsck-root.service I see:
StandardOutput=journal+console
which results in:
systemd-fsck[116]: /dev/sda2: clean, 435608/1310720 files,
3375994/5242112 blocks
being output over the to
On Wed, Mar 13, 2013 at 6:09 AM, Andrey Wagin wrote:
> 2013/3/13 Kay Sievers
>>
>> On Tue, Mar 12, 2013 at 9:35 PM, Andrey Wagin wrote:
>> > According to netlink(7) nl_groups is a bit mask with every bit
>> > representing
>> > a netlink group number.
>>
>> Netlink uses "numbers" not "a mask" sin
'Twas brillig, and Canek Peláez Valdés at 13/03/13 03:40 did gyre and
gimble:
> On Tue, Mar 12, 2013 at 9:08 PM, Zbigniew Jędrzejewski-Szmek
> wrote:
>> On Mon, Mar 11, 2013 at 03:25:48PM +0100, Lennart Poettering wrote:
>>> On Sun, 10.03.13 11:29, Canek Peláez Valdés (can...@gmail.com) wrote:
>>>
No need to try to stop systemd-sysctl on shutdown as
this service doesn't have ExecStop= anyways.
---
units/systemd-sysctl.service.in |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/units/systemd-sysctl.service.in b/units/systemd-sysctl.service.in
index 45e1ceb..d914553 10
On Mar 13, 2013 5:55 PM, "Harald Hoyer" wrote:
>
> Am 13.03.2013 09:53, schrieb Tom Gundersen:
> > This looks good. However, how do you deal with btrfs? Instal a fake
fsck?
> >
>
> that is no problem, as systemd-fsck just skips btrfs because of the
missing
> fsck.btrfs
Ah, great! My brain needs u
Am 13.03.2013 09:53, schrieb Tom Gundersen:
> This looks good. However, how do you deal with btrfs? Instal a fake fsck?
>
that is no problem, as systemd-fsck just skips btrfs because of the missing
fsck.btrfs
___
systemd-devel mailing list
systemd-devel
This looks good. However, how do you deal with btrfs? Instal a fake fsck?
On Mar 8, 2013 2:14 AM, wrote:
>
> From: Harald Hoyer
>
> ---
> src/fstab-generator/fstab-generator.c | 14 --
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/src/fstab-generator/fstab-gene
Am 08.03.2013 10:50, schrieb har...@redhat.com:
> From: Harald Hoyer
>
> ---
> src/cryptsetup/cryptsetup-generator.c | 209
> +++---
> 1 file changed, 65 insertions(+), 144 deletions(-)
>
pushed
___
systemd-devel mailing
Am 13.03.2013 09:06, schrieb Tom Gundersen:
> On Wed, Mar 13, 2013 at 3:41 AM, wrote:
>> From: Harald Hoyer
>>
>> Instead of using local-fs*.target in the initrd, use root-fs.target for
>> sysroot.mount and initrd-fs.target for /sysroot/usr and friends.
>>
>> Using local-fs.target would mean to
On Wed, Mar 13, 2013 at 3:41 AM, wrote:
> From: Harald Hoyer
>
> Instead of using local-fs*.target in the initrd, use root-fs.target for
> sysroot.mount and initrd-fs.target for /sysroot/usr and friends.
>
> Using local-fs.target would mean to carry over the activated
> local-fs.target to the is
32 matches
Mail list logo
