On 05/11/2019 23.12, Will Godfrey wrote:
> I suspect the *actual* delay is connected with networking, but with systemD>
> I'm totally lost as to where everything is, so any help would be greatly
> appreciated.
Try 'systemd-analyze blame' then. And check the journal (journalctl -b0).
Jacek
_
On Wed, 6 Nov 2019 09:25:07 +0100
Jacek Konieczny wrote:
>On 05/11/2019 23.12, Will Godfrey wrote:
>> I suspect the *actual* delay is connected with networking, but with systemD>
>> I'm totally lost as to where everything is, so any help would be greatly
>> appreciated.
>
>Try 'systemd-analyze
Done with:
systemctl disable dhcpd.service
Total time now is 17 seconds.
Thanks for your help.
--
It wasn't me! (Well actually, it probably was)
... the hard part is not dodging what life throws at you,
but trying to catch the good bits.
___
On Wed, Nov 6, 2019 at 7:19 AM Will J Godfrey
wrote:
>
> Done with:
> systemctl disable dhcpd.service
>
Do you now have to set static IPs on any interface you want to use?
I use a good amount of Pi boxes and, even when I set a static on either the
eth or wifi interface, I like to have t
On Wed, 6 Nov 2019 10:24:36 -0500
drew Roberts wrote:
>On Wed, Nov 6, 2019 at 7:19 AM Will J Godfrey
>wrote:
>
>>
>> Done with:
>> systemctl disable dhcpd.service
>>
>
>Do you now have to set static IPs on any interface you want to use?
>
>I use a good amount of Pi boxes and, even when