On Wed, Feb 4, 2015 at 2:41 PM, Patrik Flykt
wrote:
>
> Hi,
>
> On Tue, 2015-02-03 at 17:27 +0100, Lennart Poettering wrote:
>> > Is the resume event detected somehow in systemd?
>>
>> The kernel unfortunately provides no API for this right now. However,
>> if logind is the one suspending
Hi,
On Tue, 2015-02-03 at 17:27 +0100, Lennart Poettering wrote:
> > Is the resume event detected somehow in systemd?
>
> The kernel unfortunately provides no API for this right now. However,
> if logind is the one suspending the machine, then it sends out a
> PrepareForSleep() signal b
True, but it's better than nothing.
Well, I guess systemd-networkd doing basic things will have to wait on
kdbus :-)
On Tue, Feb 3, 2015 at 3:32 PM, Lennart Poettering
wrote:
> 1;3802;0cOn Tue, 03.02.15 14:38, Charles Devereaux (syst...@guylhem.net)
> wrote:
>
> > On Tue, Feb 3, 2015 at 2:29
1;3802;0cOn Tue, 03.02.15 14:38, Charles Devereaux (syst...@guylhem.net) wrote:
> On Tue, Feb 3, 2015 at 2:29 PM, Lennart Poettering
> wrote:
>
> > I am pretty sure signals are not a particularly good interface for
> > this. We should add a proper bus API for this one day, but this kinda
> > has
On Tue, Feb 3, 2015 at 2:29 PM, Lennart Poettering
wrote:
> I am pretty sure signals are not a particularly good interface for
> this. We should add a proper bus API for this one day, but this kinda
> has to wait until kdbus is a done deal, since networkd runs in early
> boot, and dbus-daemon is
On Tue, 03.02.15 14:15, Charles Devereaux (syst...@guylhem.net) wrote:
> My current solution with dhcpcd is a sleep service sending signals to
> dhcpcd (give back the lease/reclaim it), something which could be extended
> to systemd-networkd, with other signals for other meanings that you may not
My current solution with dhcpcd is a sleep service sending signals to
dhcpcd (give back the lease/reclaim it), something which could be extended
to systemd-networkd, with other signals for other meanings that you may not
want by default, like:
- removing the configuration it did (which is currentl
On Tue, 03.02.15 18:20, Patrik Flykt (patrik.fl...@linux.intel.com) wrote:
> On Tue, 2015-02-03 at 11:46 +0100, Lennart Poettering wrote:
> > On Mon, 02.02.15 23:12, Charles Devereaux (syst...@guylhem.net) wrote:
> >
> > > Another problem with systemd-networkd is that the lease is not renewed
> >
On Tue, 2015-02-03 at 11:46 +0100, Lennart Poettering wrote:
> On Mon, 02.02.15 23:12, Charles Devereaux (syst...@guylhem.net) wrote:
>
> > Another problem with systemd-networkd is that the lease is not renewed
> > after sleep.
> >
> > This is a basic feature, a laptop is frequently physicially m
On Mon, 02.02.15 23:12, Charles Devereaux (syst...@guylhem.net) wrote:
> Another problem with systemd-networkd is that the lease is not renewed
> after sleep.
>
> This is a basic feature, a laptop is frequently physicially moved, which
> means another DHCP lease should be acquired, but I don't se
Another problem with systemd-networkd is that the lease is not renewed
after sleep.
This is a basic feature, a laptop is frequently physicially moved, which
means another DHCP lease should be acquired, but I don't see how to do that.
How can I make that happen? It's not clear to me, since systemd
On Sun, 11.01.15 18:45, Charles Devereaux (syst...@guylhem.net) wrote:
> What's not is the time it takes to systemd-networkd : 1 second for IPv6 is
> acceptable (I'm using SLAAC with radvd on the other end), but for ipv4 it's
> more like 3 seconds, plus another 3 to use the proper DNS server (!!)
Hello
With dhcpcd5 and the following options, once wpa_supplicant is done, I
have a connection within the same second if I ignore ARP.
With systemd-network, it's much much slower.
$ systemd-analyze blame
3.923s systemd-networkd-wait-online.service
(...)
I tried to measure the time ta
13 matches
Mail list logo
