> On 12 Apr 2024, at 05:42, Mike Wright wrote:
>
> Reason is because .socket files will activate their corresponding service
> files REGARDLESS of masking or disabling.
A masked service cannot do anything as masking replaced it with /dev/null.
Barry
--
> On 11 Apr 2024, at 12:59, Sam Varshavchik wrote:
>
> What I do see, though, is that we have both NetworkManager-wait-online and
> systemd-networkd-wait-online. Why do we need both of them?
It's odd that both are enabled.
On my kde plasma Vm only NetworkManager-wait-online.service is
On 4/11/24 15:08, Jeffrey Walton wrote:
On Thu, Apr 11, 2024 at 6:01 PM Sam Varshavchik wrote:
Tim via users writes:
"The service systemd-networkd-wait-online.service invokes systemd-
networkd-wait-online without any options. Thus, it waits for all
managed interfaces to be configured or
On Thu, Apr 11, 2024 at 6:01 PM Sam Varshavchik wrote:
>
> Tim via users writes:
>
> > "The service systemd-networkd-wait-online.service invokes systemd-
> > networkd-wait-online without any options. Thus, it waits for all
> > managed interfaces to be configured or failed, and for at least one to
Tim via users writes:
"The service systemd-networkd-wait-online.service invokes systemd-
networkd-wait-online without any options. Thus, it waits for all
managed interfaces to be configured or failed, and for at least one to
be online."
Could it be that you have some additional interfaces
On Thu, 2024-04-11 at 07:59 -0400, Sam Varshavchik wrote:
> What I do see, though, is that we have both NetworkManager-wait-
> online and systemd-networkd-wait-online. Why do we need both of them?
>
> I simply disabled systemd-networkd-wait-online, and that seems to
> solve the problem.
Roger Heflin writes:
Run this:
systemd-analyze critical-chain network-online.target
Can you explain why you think inspecting dependencies and starting times of
different systemd units would have any bearing on why a single unit, systemd-
network, is blowing chunks? Wasn't it clear from my
Run this:
systemd-analyze critical-chain network-online.target
On Wed, Apr 10, 2024 at 6:20 AM Sam Varshavchik wrote:
>
> Samuel Sieb writes:
>
> > I have a similar problem where the wait-online service suddenly started
> > taking a very long time and then failing. My system that used to boot
Samuel Sieb writes:
I have a similar problem where the wait-online service suddenly started
taking a very long time and then failing. My system that used to boot in a
few seconds now takes over a minute. So I have two questions.
What is it waiting for? My main ethernet card gets an
Tim via users writes:
On Tue, 2024-04-09 at 22:12 -0400, Sam Varshavchik wrote:
>
> Everything comes up normally. Network connectivity on this box is normal.
> Originally I was looking into why it took a long time for keepalived to
come
> up on this box and grab its virtual IP address, and I
On Tue, 2024-04-09 at 23:20 -0700, Samuel Sieb wrote:
> Perhaps more importantly, why can't that happen in the background? Why
> does gdm care if the network is connected?
It'd need to be *if* people are using a network share for their
homespace, or other "expected to be there" directories.
On 4/9/24 19:12, Sam Varshavchik wrote:
I've been made aware that it takes two minutes for
systemd-networkd-wait-online.service to spin its wheels, before giving
up with a squeal:
Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting
systemd-networkd-wait-online.service - Wait for
On Tue, 2024-04-09 at 22:12 -0400, Sam Varshavchik wrote:
> I've been made aware that it takes two minutes for systemd-networkd-wait-
> online.service to spin its wheels, before giving up with a squeal:
>
> Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting
>
I've been made aware that it takes two minutes for systemd-networkd-wait-
online.service to spin its wheels, before giving up with a squeal:
Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting
systemd-networkd-wait-online.service - Wait for Network to be Configured…
Apr 09 22:05:30
14 matches
Mail list logo
