You are not logged in.
Hey,
my boot time is usually < 10 sec, but the network connection takes about 2 minutes to fully establish.
I connect via LAN and use pdnsd as a DNS caching service, which itself uses TOR to resolve requests. NetworkManager is then used to toggle my VPN when needed. When my connection is finally established and I want to use my VPN, I must connect to my VPN, de- and reactivate the LAN connection and connect to the VPN again, in order to actually be connected via VPN.
[klemens@arch-pc ~]$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1min 37.382s
└─multi-user.target @1min 37.382s
└─pdnsd.service @1min 30.299s
└─tor.service @1min 30.299s
└─network.target @1min 30.298s
└─NetworkManager.service @834ms +2.861s
└─basic.target @833ms
└─timers.target @833ms
└─systemd-tmpfiles-clean.timer @833ms
└─sysinit.target @828ms
└─sys-fs-fuse-connections.mount @8.331s +812us
└─system.slice @98ms
└─-.slice @98ms
Can anybody tell me what causes this strange behaviour? It did not always take that much time, but I can't tell when it changed.
Offline
One possibility https://wiki.archlinux.org/index.php/Sy … _over_time
https://ugjka.net
"It is easier to fool people, than to convince them that they've been fooled" ~ Dr. Andrea Love
Offline
My /var/log/journal doesn't even exist, as /var/log/ gets mounted as ramfs in RAM on boot.
Offline
Can anybody help?
Offline
No idea? Any hint what causes this need of reactivation for the VPN connection?
Offline