I try to download a file with curl directly after logging into Gnome. This usually fails because mostly the WiFi connection is only established after login. If I wait long enough in the login screen before logging in, the connection is already established and the download works.
So far I have used Manjaro. WiFi was already active long before the login screen of GDM was even displayed. The download therefore always worked.
The download is initiated with a *.desktop file in ~/.config/autostart.
Is there another way to start the download after the user is logged in and the WiFi connection is really ready?
Create a systemd user unit that waits for the network-online.target.
A script something like:
[Unit] Description=Startup script Requires=network-online.target After=network-online.target [Service] Type=oneshot # either simple or oneshot, but sounds like oneshot ExecStart=/home/<user>/script.sh RemainAfterExit=yes #if oneshot, otherwise no [install] WantedBy=default.targetEdit the template according to your needs and dump it into
~/.local/share/systemd/user/<unit>.serviceand enable it withsystemctl --user enable --now <unit>What’s the difference between oneshot and simple?
Oneshot services are for things like scripts that do a thing and exit. Simple is for basic services that intend to run for the lifetime of the system (or for user units, the lifetime of the user’s session).
Ahh ok. Since in this case the script should only run at start and then exit, I use oneshot. Many thx.
You can have your WiFi start with the rest of your network service before login if you choose. Maybe that’s the limitation here.
The simplest solution is probably a script that waits and retries until curl succeeds.
Nice. I will try the systemd unit. Meanwhile, i have added a loop in the script, which helps a little bit:
maxwait=15 if [[ $(nm-online -x) != *"online"* ]]; then echo "missing internet connection, waiting..." for (( i = 1; i <= maxwait; ++i )); do sleep 1 & echo $i if [[ $(nm-online -x) == *"online"* ]]; then break fi if [[ $i -eq $maxwait ]]; then echo "No internet connection" exit 1 fi wait done fiIn my test, this exits the script after 15 seconds without connection, but continues, when the connection is available or is established within this time.
But i think, its a nice idea, to add this to the script AND use the systemd unit together.
With these kinds of things, where you need to manage state (waiting, executing, failed, etc), it is very easy to miss a case or transition and generally better to rely on proven tech.
Let the waiting for network connection and retrying be done by systemd, half the internet runs on it. You can trust that it won’t mess that part up. Write only what is specific to you in your script.
Easiest way would be to just add a
sleep 15command at the top of the script. Time how long it takes your wifi to come up, and adjust the sleep time with like a 2-3 second buffer in case it takes linger for some reason.More exact would be to create a systemd service for your script that depends on network connectivity to execute.
Yep, I know. But when I only depend on
After=network-online.target Wants=network-online.targetthis doesn’t mean, I have a working internet connection. That’s why the loop.
Or is that wrong?
