- User Since
- Sep 15 2018, 11:31 PM (94 w, 4 d)
Sun, Jul 5
This PR should correct the issue.
It should. This should really be a non-breaking change as it's a fallback for something else that already exists in /etc/hosts.
Sat, Jul 4
default as an IP address is in the end more useful then a resolved PTR
This also has a measurable impact on CPU
Fri, Jul 3
To add to this, this link pointed me at the correct solution:
Sat, Jun 27
Go for it. Just to confirm, this did work on the rolling from the 8th of this month, so it was something that got gobbled up in the rewrite.
Then I believe the best course of action is to restore that error condition, but have it reference the “alias” config then.
To add, maybe it's just the content of the error message that's misleading here if there other ways to do it. Or maybe the problem is that there are multiple ways to accomplish this
I guess there's two ways to approach it. This is the correct way:
This PR should correct.
Fri, Jun 19
Thu, Jun 18
Revising this since I nailed down the issue.
Wed, Jun 17
Can confirm. This bug is corrected in the the latest rollings (for at least a month or more)
Wed, Jun 10
Jun 9 2020
This one works good too
Seems like this might be VRF related
Jun 8 2020
Changed this around a bit to load the modules automatically if necessary. Only adds about half a second to initial execution
Jun 7 2020
Jun 4 2020
May 20 2020
This PR419 should take care of this and the parent task
No worries. I think I've got a simple fix for this. Just needed to step away for a bit
This is related to this change:
PR416 should be the real fix here and PR413 should be reverted.
May 19 2020
Yep. Confirmed, and that's the root issue here.
This PR should hopefully correct this.
May 16 2020
@dmbaturin Maybe just anything that contains systemctl? Surely 100% of those will need it. But that also assumes anything called via /usr/lib/python3/dist-packages/vyos/util.py
PR510 should add the necessary sudo
May 12 2020
This was a breaking change
May 8 2020
PR405 corrects this
Apr 30 2020
This PR should address this simple usability enhancement
Apr 29 2020
Apr 8 2020
Looks good. I don't have merge access but this definitely is a fix to an oversight in the build.
Apr 4 2020
Sure, go ahead. Thanks!
Mar 31 2020
Mar 30 2020
If this is a duplicate of something, go ahead and close it
PR283 should fix this.
Mar 23 2020
PR260 should fix this
PR259 fixes this
Mar 22 2020
Can confirm that this can be closed now.
Mar 21 2020
Personally this is behavior I agree with.