On 07/05/19 6:23 pm, Arnaud Lemaire wrote:
Hi there,
I'm trying to set up network multipath routing with systemd, but I
cannot find a way to do it cleanly.
The part that I cannot set up is :
```
$ ip route
default
nexthop via 192.168.11.1 dev inet.11 weight 5
nexthop via
Thx I will try that, but it looks a little bit hackish.
No way to set the multipath routing with systemd-networkd?
If no, is it expected ? a feature request ? a bug ?
On Tue, May 7, 2019 at 3:23 PM Mantas Mikulėnas wrote:
> On Tue, May 7, 2019 at 3:54 PM Arnaud Lemaire wrote:
>
>> Hi there,
On Mon, May 6, 2019 at 10:56 PM Andrei Borzenkov
wrote:
> 07.05.2019 4:22, Matt Zagrabelny пишет:
>
> > Is there a way to have systemd-network assign addressing to an interface
> > without the link being up?
> >
>
> man systemd.network
>
>ConfigureWithoutCarrier=
>A boolean.
On Tue, May 7, 2019 at 10:55 AM Jeffrey Walton wrote:
>
> As far as I know the instruction is only defined for Intel, AMD and
> Hyogen cpus. See, for example,
> https://github.com/weidai11/cryptopp/blob/master/cpu.cpp#L380.
>
Jeff,
I think you missed my point. The rdrand instruction is _not_
On Tue, May 7, 2019 at 10:27 AM Segher Boessenkool
wrote:
> But it should not execute it, it is guarded by some cpuid things.
>
> If the assembler does not like the insn, first do (in the same asm) an
> assembler pseudo-instruction to select a CPU that does have that insn,
> then the rdrand, and
On Mo, 06.05.19 12:09, Mantas Mikulėnas (graw...@gmail.com) wrote:
> > Am 03.05.19 um 13:29 schrieb Jérémy ROSEN:
> > > if you want the whole power of structured logs, you need to use the
> > journald API
> >
>
> On the other hand, JSON parsing might be a useful addition to journald, as
>
On Di, 07.05.19 08:50, tedheadster (tedheads...@gmail.com) wrote:
> GCC and systemd teams:
> I compiled systemd-241 and expressly set march=winchip-c6 (an i486
> class cpu). It generated illegal instructions (rdrand) in the code.
> Oddly, it does NOT do this when I set march=i486:
>
> Dump of
On Tue, May 7, 2019 at 3:54 PM Arnaud Lemaire wrote:
> Hi there,
>
> I'm trying to set up network multipath routing with systemd, but I cannot
> find a way to do it cleanly.
>
> The part that I cannot set up is :
> ```
> $ ip route
> default
> nexthop via 192.168.11.1 dev inet.11 weight
Hi there,
I'm trying to set up network multipath routing with systemd, but I cannot
find a way to do it cleanly.
The part that I cannot set up is :
```
$ ip route
default
nexthop via 192.168.11.1 dev inet.11 weight 5
nexthop via 192.168.22.2 dev inet.22 weight 10
...
```
I'm
GCC and systemd teams:
I compiled systemd-241 and expressly set march=winchip-c6 (an i486
class cpu). It generated illegal instructions (rdrand) in the code.
Oddly, it does NOT do this when I set march=i486:
Dump of assembler code for function rdrand:
0xb7e21440 <+0>: push %esi
On Mo, 06.05.19 09:12, Thomas Güttler (guettl...@thomas-guettler.de) wrote:
> Solution 1:
> My service (written Python) uses the journald API.
> Disadvantage: My script can't be run under a different environment
> (without journald)
Doesn't Python have an abstraction for that that does some
On Tue, May 7, 2019 at 10:40 AM Thomas Güttler
wrote:
> Hi Mantas Mikulėnas and other members,
>
> This looks nice:
>
>@cee: {}
>
> For me this is new. I could find some scattered information about this.
>
> Is there an official spec for this logging syntax?
>
I believe it's called "CEE log
Hi Mantas Mikulėnas and other members,
This looks nice:
@cee: {}
For me this is new. I could find some scattered information about this.
Is there an official spec for this logging syntax?
I think it would be nice if a systemd service could log structured logs like
this via stdout.
13 matches
Mail list logo
