On Fri, Sep 9, 2022 at 11:36 PM Andrea Pappacoda
wrote:
> Il giorno ven 9 set 2022 alle 12:17:42 -05:00:00, Greg Oliver
> ha scritto:
> > Well, easiest to explain is user apps that use tcp or udp sockets to
> > communicate. If they are on the same host, then huge gains can be
> > achieved by us
Il giorno ven 9 set 2022 alle 12:17:42 -05:00:00, Greg Oliver
ha scritto:
Well, easiest to explain is user apps that use tcp or udp sockets to
communicate. If they are on the same host, then huge gains can be
achieved by using the loopback adapter (especially TCP comms).
Thanks, but again, i
On Fri, Sep 09, 2022 at 12:17:42PM -0500, Greg Oliver wrote:
> Il giorno ven 9 set 2022 alle 17:37:14 +02:00:00, Lennart Poettering
> <[2]lenn...@poettering.net> ha scritto:
> > People sometimes route stuff onto the loopback device in addition to
> > the the usual [3]127.0.0.0/8
On Fri, Sep 9, 2022 at 10:40 AM Andrea Pappacoda wr
> Il giorno ven 9 set 2022 alle 17:37:14 +02:00:00, Lennart Poettering
> ha scritto:
> > People sometimes route stuff onto the loopback device in addition to
> > the the usual 127.0.0.0/8 traffic so that it ends up on local sockets.
>
> Thanks
On 09.09.2022 16:19, Andrei Borzenkov wrote:
> "Requires" means - submit additional start jobs for the listed units
> and wait until these start jobs are completed before processing the
> start job for the unit itself.
Sorry, that was wrong. That is what everyone assumes it does.
Requires means -
Il giorno ven 9 set 2022 alle 17:37:14 +02:00:00, Lennart Poettering
ha scritto:
People sometimes route stuff onto the loopback device in addition to
the the usual 127.0.0.0/8 traffic so that it ends up on local sockets.
Thanks for the reply, but I don't fully understand the implications of
t
On Fr, 09.09.22 14:45, Andrea Pappacoda (and...@pappacoda.it) wrote:
> Hi all,
>
> yesterday I was playing a bit with systemd-network, and I noticed that it is
> possible for it to manage the loopback interface. Is it useful in any way?
> Should the loopback interface be managed in systems where s
On Fri, Sep 9, 2022 at 4:12 PM Ulrich Windl
wrote:
> Thanks for the explanation! For me part of the problem is: Where is "pull in"
> defined? ;-)
In an English dictionary?
> The phrase is used for Wants, but also for Requires. So is "pull in " a
> synonym for "wants or requires"?
Yes. "Pull
>>> Michael Biebl schrieb am 09.09.2022 um 14:15 in Nachricht
:
> Am Fr., 9. Sept. 2022 um 14:12 Uhr schrieb Michael Biebl :
>>
>> Am Fr., 9. Sept. 2022 um 14:01 Uhr schrieb Ulrich Windl
>> :
>> >
>> > >>> Andrei Borzenkov schrieb am 09.09.2022 um 13:41
>> > >>> in
>> > Nachricht
>> > :
>> > > O
Am Fr., 9. Sept. 2022 um 14:12 Uhr schrieb Michael Biebl :
>
> Am Fr., 9. Sept. 2022 um 14:01 Uhr schrieb Ulrich Windl
> :
> >
> > >>> Andrei Borzenkov schrieb am 09.09.2022 um 13:41 in
> > Nachricht
> > :
> > > On Fri, Sep 9, 2022 at 2:13 PM Ulrich Windl
> > > wrote:
> > > ...
> > >> >
> > >> >
Am Fr., 9. Sept. 2022 um 14:01 Uhr schrieb Ulrich Windl
:
>
> >>> Andrei Borzenkov schrieb am 09.09.2022 um 13:41 in
> Nachricht
> :
> > On Fri, Sep 9, 2022 at 2:13 PM Ulrich Windl
> > wrote:
> > ...
> >> >
> >> > If you are interested in services that pull in e.g. time-sync.target
> >> > via Wan
>>> Andrei Borzenkov schrieb am 09.09.2022 um 13:41 in
Nachricht
:
> On Fri, Sep 9, 2022 at 2:13 PM Ulrich Windl
> wrote:
> ...
>> >
>> > If you are interested in services that pull in e.g. time-sync.target
>> > via Wants (or Requires) and order themselves before the target, you
>> > can use some
On Fri, Sep 9, 2022 at 2:13 PM Ulrich Windl
wrote:
...
> >
> > If you are interested in services that pull in e.g. time-sync.target
> > via Wants (or Requires) and order themselves before the target, you
> > can use something like
> > $ systemctl show time-sync.target -p WantedBy -p RequiredBy -p
>>> Michael Biebl schrieb am 09.09.2022 um 12:54 in
Nachricht
:
> Am Fr., 9. Sept. 2022 um 12:31 Uhr schrieb Michael Biebl
:
>>
>> Am Fr., 9. Sept. 2022 um 12:08 Uhr schrieb Ulrich Windl
>> :
>> >
>> > >>> Michael Biebl schrieb am 09.09.2022 um 10:55 in
>> > Nachricht
>> > :
>> > > Example: syslo
>>> Michael Biebl schrieb am 09.09.2022 um 12:31 in
Nachricht
:
> Am Fr., 9. Sept. 2022 um 12:08 Uhr schrieb Ulrich Windl
> :
>>
>> >>> Michael Biebl schrieb am 09.09.2022 um 10:55 in
>> Nachricht
>> :
>> > Example: syslog.service
>> >
>> > $ systemctl status syslog.service
>> > ● rsyslog.service
Am Fr., 9. Sept. 2022 um 12:31 Uhr schrieb Michael Biebl :
>
> Am Fr., 9. Sept. 2022 um 12:08 Uhr schrieb Ulrich Windl
> :
> >
> > >>> Michael Biebl schrieb am 09.09.2022 um 10:55 in
> > Nachricht
> > :
> > > Example: syslog.service
> > >
> > > $ systemctl status syslog.service
> > > ● rsyslog.ser
Am Fr., 9. Sept. 2022 um 12:08 Uhr schrieb Ulrich Windl
:
>
> >>> Michael Biebl schrieb am 09.09.2022 um 10:55 in
> Nachricht
> :
> > Example: syslog.service
> >
> > $ systemctl status syslog.service
> > ● rsyslog.service - System Logging Service
> > Loaded: loaded (/lib/systemd/system/rsyslo
>>> Michael Biebl schrieb am 09.09.2022 um 10:55 in
Nachricht
:
> Example: syslog.service
>
> $ systemctl status syslog.service
> ● rsyslog.service - System Logging Service
> Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled;
> preset: enabled)
> Active: active (running) sinc
Yes, this. There's no benefit to disabling link-local addressing, and
doing so can definitely break other IPv6 features. I've never seen an
explicitly-configured link-local address before, but I'd be really
surprised if it worked as a replacement for the
automatically-generated link-local address
Example: syslog.service
$ systemctl status syslog.service
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled;
preset: enabled)
Active: active (running) since Thu 2022-09-08 08:55:45 CEST; 1 day 1h ago
TriggeredBy: ● syslog.socket
>>> Michael Biebl schrieb am 09.09.2022 um 10:30 in Nachricht
:
> I'd probably just use `systemctl status`
Can you give some details? I don't see what I'm expecting to see.
Regards,
Ulrich
>
> Am Fr., 9. Sept. 2022 um 10:18 Uhr schrieb Ulrich Windl
> :
>>
>> Hi!
>>
>> I'm wondering: having so
I'd probably just use `systemctl status`
Am Fr., 9. Sept. 2022 um 10:18 Uhr schrieb Ulrich Windl
:
>
> Hi!
>
> I'm wondering: having some specific target, e.g. time-set.target, how can I
> find out what actually "provides" that target?
> I see that I can query what "requires" the given target, bu
Hi!
I'm wondering: having some specific target, e.g. time-set.target, how can I
find out what actually "provides" that target?
I see that I can query what "requires" the given target, but how to I get the
other direction?
I mean by using a tool like systemctl, not by finding and grepping some
d
23 matches
Mail list logo
