Is that something that could be added to modprobe.conf to have it work right without any modprobe calls?
Yes, that's how I do it. But that just switches the mode to one that supports virtual interfaces, I still need to add the virtual interface, and I can't do that in a modprobe conf.
To be fair such race condition could have happened in any init system.
I feel like it's really easy to make that happen under systemd if you're not completely on the ball, where as it's more difficult in things like openrc.
Yeah I've also been burned not having RemainAfterExit=y in a oneshot unit. What's worse, such an unit can get started multiple times.
You live and you learn, on its own something like that isn't a huge problem.
Perhaps having a dependency to start your service before network-manager would have solved this.
It was one in a long-chain of similar issues, but yes. There are a lot of ways I probably could have made this work, but at the end of the day I'm still writing shell scripts and not using very many of systemd's "helpful" features.
Comments
Yes, that's how I do it. But that just switches the mode to one that supports virtual interfaces, I still need to add the virtual interface, and I can't do that in a modprobe conf.
I feel like it's really easy to make that happen under systemd if you're not completely on the ball, where as it's more difficult in things like openrc.
You live and you learn, on its own something like that isn't a huge problem.
It was one in a long-chain of similar issues, but yes. There are a lot of ways I probably could have made this work, but at the end of the day I'm still writing shell scripts and not using very many of systemd's "helpful" features.