В Sun, 8 Jun 2014 01:42:18 +0200
Michael Biebl пишет:
> 2014-06-08 1:07 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
> > On Sun, Jun 08, 2014 at 12:55:55AM +0200, Michael Biebl wrote:
> >> Could you elaborate why Before=network.target is too late?
> > Because then network setup races with e.g. iptable
On Sun, Jun 08, 2014 at 09:16:43AM +0800, Aaron Lewis wrote:
> Date: Sun, 8 Jun 2014 09:16:43 +0800
> From: Aaron Lewis
> To: [email protected]
> Subject: [systemd-devel] Disable IPv6?
>
> Hi,
>
> Every time I boot I can see a 'failed to insert ipv6 module' message,
> pretty an
On Sun, Jun 8, 2014 at 4:16 AM, Aaron Lewis wrote:
> Hi,
>
> Every time I boot I can see a 'failed to insert ipv6 module' message,
> pretty annoying
> I want to disable IPv6 service, is that possible?
No, not unless you remove it from "kmod-setup.c".
> For the record, I disabled IPv6 intentional
Hi,
Every time I boot I can see a 'failed to insert ipv6 module' message,
pretty annoying
I want to disable IPv6 service, is that possible?
For the record, I disabled IPv6 intentionally in my customized kernel
--
Best Regards,
Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
Finger Print:
There are. You have socket-activated services, and you have services that
bind to 0.0.0.0 or ::, and you have services that make use of IP_FREEBIND
to avoid having to wait for addresses to be assigned...
--
Mantas Mikulėnas
On Jun 8, 2014 2:27 AM, "Leonid Isaev" wrote:
> On Sun, Jun 08, 2014 a
On Sat, Jun 07, 2014 at 07:27:32PM -0400, Leonid Isaev wrote:
> On Sun, Jun 08, 2014 at 01:07:38AM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> > Date: Sun, 8 Jun 2014 01:07:38 +0200
> > From: Zbigniew Jędrzejewski-Szmek
> > To: Michael Biebl
> > Cc: systemd Mailing List
> > Subject: Re: [systemd
2014-06-08 1:07 GMT+02:00 Zbigniew Jędrzejewski-Szmek :
> On Sun, Jun 08, 2014 at 12:55:55AM +0200, Michael Biebl wrote:
>> Could you elaborate why Before=network.target is too late?
> Because then network setup races with e.g. iptables setup. Depending
> on the timing, a window in which the networ
On Sun, Jun 08, 2014 at 01:07:38AM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> Date: Sun, 8 Jun 2014 01:07:38 +0200
> From: Zbigniew Jędrzejewski-Szmek
> To: Michael Biebl
> Cc: systemd Mailing List
> Subject: Re: [systemd-devel] [PATCH] Add a network-pre.target to avoid
> firewall leaks
> User
On Sat, Jun 7, 2014 at 8:49 AM, Leslie Zhai wrote:
> [...]
> But I do NOT know how to hook coredump in user space...
> I simply cat /proc/sys/kernel/core_pattern
> |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
>
> Then systemd-coredump collector will be called (HOOKed), for example,
> BANG
On Sun, Jun 08, 2014 at 12:55:55AM +0200, Michael Biebl wrote:
> Could you elaborate why Before=network.target is too late?
Because then network setup races with e.g. iptables setup. Depending
on the timing, a window in which the network has been set up, but
the firewall is not yet in place.
Zbysz
Could you elaborate why Before=network.target is too late?
Am 06.06.2014 14:53 schrieb "Rusty Bird" :
> https://bugs.freedesktop.org/show_bug.cgi?id=79600
> ---
> Makefile.am | 1 +
> man/systemd.special.xml | 1 +
> units/network-pre.target | 11 +++
On Sat, Jun 07, 2014 at 04:03:33PM +0300, Tanu Kaskinen wrote:
> On Sat, 2014-06-07 at 07:42 -0500, William Giokas wrote:
> > On Sat, Jun 07, 2014 at 01:07:08PM +0300, Tanu Kaskinen wrote:
> > > Hi,
> > >
> > > Currently, systemd symlinks ~/.local/share/systemd/user to
> > > ~/.config/systemd/user
Hi,
we *might* want to add a target like this. People often have things
which they want to do before network is configured and it would be a
convenient hook for them. But the reasons should be made
clearer. Currently my iptables.service has Before=basic.target. Why
is doing something like that no
Le Sun, 8 Jun 2014 00:21:24 +0400,
Kirill Elagin a écrit :
> `failed` is a state of a unit and as such it is documented in
> `systemd` man page.
What kind of unit ?
I quote:
>By default, it will wait for all links it is aware of and which are
>managed by systemd-networkd.service(8)
Are thes
Hi,
the coredump machinery provided by the kernel only works for
user space processes. Kernel faults usually end in a traceback
being printed to the console and are handled differently.
To receive information about past and future coredumps stored
in the journal you need to:
1. Add a filter which
`failed` is a state of a unit and as such it is documented in `systemd` man
page.
I'm not sure if `systemd` man page fits into your definition of
“associated”.
Units may be "active" (meaning started,
bound, plugged in, ..., depending on the unit type, see below), or
"
Hello. It is said in the man systemd-netword-wait-online.service:
>systemd-networkd-wait-online is a one-shot system service that waits
>for the network to be configured. By default, it will wait for all
>links it is aware of and which are managed by
>systemd-networkd.service(8) to be fully config
On Sat, Jun 07, 2014 at 06:58:50PM +0200, Daniel Mack wrote:
> Hi Djalal,
>
> On 06/07/2014 06:47 PM, Djalal Harouni wrote:
> > I'm sending this to have some updates on the policy!
> >
> > I did notice some issues and others still *to confirm*, so first I'm
> > writing some policy tests to make s
Hi Djalal,
On 06/07/2014 06:47 PM, Djalal Harouni wrote:
> I'm sending this to have some updates on the policy!
>
> I did notice some issues and others still *to confirm*, so first I'm
> writing some policy tests to make sure we don't break. I'll clean what
> I've and get get back to you.
Sure,
On Sat, Jun 07, 2014 at 06:29:21PM +0200, Daniel Mack wrote:
> On 06/07/2014 06:26 PM, Djalal Harouni wrote:
> > Signed-off-by: Djalal Harouni
>
> Applied, thanks!
Oh that was quick!
This answers my first question of the other email!
Thanks Daniel!
> > ---
> > policy.c | 9 +++--
> > 1 fi
Hi,
I'm sending this to have some updates on the policy!
I did notice some issues and others still *to confirm*, so first I'm
writing some policy tests to make sure we don't break. I'll clean what
I've and get get back to you.
For the moment can you please confirm:
1) I assume the policy.c on
On 06/07/2014 06:26 PM, Djalal Harouni wrote:
> Signed-off-by: Djalal Harouni
Applied, thanks!
> ---
> policy.c | 9 +++--
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/policy.c b/policy.c
> index 5a9770d..6f2bb1f 100644
> --- a/policy.c
> +++ b/policy.c
> @@ -10,11 +1
Signed-off-by: Djalal Harouni
---
policy.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/policy.c b/policy.c
index 5a9770d..6f2bb1f 100644
--- a/policy.c
+++ b/policy.c
@@ -10,11 +10,8 @@
* your option) any later version.
*/
-#include
#include
-#include
#
On Sat, 2014-06-07 at 07:42 -0500, William Giokas wrote:
> On Sat, Jun 07, 2014 at 01:07:08PM +0300, Tanu Kaskinen wrote:
> > Hi,
> >
> > Currently, systemd symlinks ~/.local/share/systemd/user to
> > ~/.config/systemd/user. I'd prefer to not have that symlink. I'd want the
> > two locations have
On Sat, Jun 07, 2014 at 01:07:08PM +0300, Tanu Kaskinen wrote:
> Hi,
>
> Currently, systemd symlinks ~/.local/share/systemd/user to
> ~/.config/systemd/user. I'd prefer to not have that symlink. I'd want the
> two locations have different semantics, analogous to the separation between
> /usr/lib/s
https://bugs.freedesktop.org/show_bug.cgi?id=79600
---
Makefile.am | 1 +
man/network-pre.target.xml| 82 +++
units/network-pre.target | 11 ++
units/network.target | 8
units/systemd-networkd.servic
Andrey Borzenkov:
> В Fri, 06 Jun 2014 12:53:01 +
> Rusty Bird пишет:
>> --- a/man/systemd.special.xml
>> +++ b/man/systemd.special.xml
>> @@ -71,6 +71,7 @@
>> local-fs-pre.target,
>> multi-user.target,
>> network.target,
>> +n
Hi,
Currently, systemd symlinks ~/.local/share/systemd/user to
~/.config/systemd/user. I'd prefer to not have that symlink. I'd want
the two locations have different semantics, analogous to the separation
between /usr/lib/systemd/user and /etc/systemd/user, i.e. service
upstreams should insta
28 matches
Mail list logo
