@danderson i'd kinda kill for something like systemd directives that does pass the socket
"StopWhenUnroutableTo=0.0.0.0/0"
"StartWhenRoutableTo=0.0.0.0/0"
etc.
but unsure where is the right design and what direction should we go
@danderson i'd kinda kill for something like systemd directives that does pass the socket
"StopWhenUnroutableTo=0.0.0.0/0"
"StartWhenRoutableTo=0.0.0.0/0"
etc.
but unsure where is the right design and what direction should we go
@erincandescent @danderson @raito And I've yet to see a service-management case where you'd need online/offline status (whatever that means). For services just need to check if networking is configured (daemon listening to a specific IP address), or even just check there's a networking stack (daemon binding to 0.0.0.0 / ::0).
Although as systemd also munched cron there's also that, but for those given that internet isn't just online/offline, better to just have the script handle that or just fail, rather than get silently disabled because systemd couldn't reach something that might have been firewalled out.
And personally I much prefer using things like runlevels to turn of groups of services, which can be network manager itself, which could get linked to an Airplane Mode button.
@lanodan @erincandescent @danderson i have plenty of those
"create an ssh tunnel once online"
"swap the http proxy settings once connected to VPN X which has a route to Y"
and currently they use a bunch of wait-for-online stuff that is not really nice and too many busy loops
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.