network changes listening task sending SIGHUP to inetd to reread conf… #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…iguration.
this helps with / fixes issues around services availability on ipv6 defined via inetd. the ipv6 takes usually longer to initialise than ipv4. so as inetd starts triggered by net config change, when it binds interfaces, ipv6 can still be in the process of bringing up. inetd then doesn't bind ipv6 sockets and services otherwise defined to be available on ipv6 are not available.
(this task receives all changes from net devices - so once ipv6 up, it tells inetd to recheck config. inetd in the process also rebinds interfaces))
testing inetd.conf:
ssh on ipv6 after boot finally works.