It almost certainly does not restart the process.
It almost certainly does not restart the process. In my short time poking around, my belief is discoveryd gets wedged into a state where it thinks DNS queries aren't resolving, and so it doesn't try to resolve them. I'm not sure what exactly is going on there, either all the queries are blocked somehow on some long-lived query that has no response and no timeout, or discoveryd thinks the network is broken and is waiting for it to come back (those are just guesses). Either way, the command tells discoveryd to restart any outstanding "questions" (which presumably means queries). When I had the issue, that was sufficient to flush out whatever it was that was blocking everything, as my machine instantly started working properly again.
Posted by eridius on Feb 10, 2015, 11:14 PM
Tags
Related issues
- I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
- [BUG] No response from API error when Advisor is triggered
- I thought the general premise is that humans can't form social groups bigger than around ~200.
- great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
- > It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
- Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
reliability (Network)
I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
[BUG] No response from API error when Advisor is triggered
I thought the general premise is that humans can't form social groups bigger than around ~200.
great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
> It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
Contrary to some other comments: no, IPV6 hasn't taken over the world at all.
Copy and paste not working
Full Offline Support
It almost certainly does not restart the process.
It almost certainly does not restart the process. In my short time poking around, my belief is discoveryd gets wedged into a state where it thinks DNS queries aren't resolving, and so it doesn't try to resolve them. I'm not sure what exactly is going on there, either all the queries are blocked somehow on some long-lived query that has no response and no timeout, or discoveryd thinks the network is broken and is waiting for it to come back (those are just guesses). Either way, the command tells discoveryd to restart any outstanding "questions" (which presumably means queries). When I had the issue, that was sufficient to flush out whatever it was that was blocking everything, as my machine instantly started working properly again.
Comments (0)
No comments yet. Start the discussion.