Hello Marius, 16.06.2016 19:04, Marius Tomaschewski:
Am 16.06.2016 um 17:59 schrieb Marius Tomaschewski:
Am 16.06.2016 um 14:42 schrieb Nikolai Zhubr: [...] But LINK_REQUIRED=no default is definitely the wrong way to go.
But now, you'll be able to set such a default for you:
Good to know, I'll definitely add it to my emergency reminder. Although it still feels somewhat hacky... I appreciate your detailed explantion of why changing the default is inacceptable and I tend to agree that your reasons are valid. But then question is, how to properly set up a most trivial ipv4-only configuration with a static (fixed forever) ip address and some trivial tcp service (say httpd) bound to this fixed ip address only? As I see it now, there are 2 choices currently: 1. Leave all per default. Works fine until one day ocasionally link happens to be temporary down at the time of booting up. The service will not be able to bind to the address it expects and will fail, which is unwise because we know our address is fixed forever anyway. 2. Manually tweak LINK_REQUIRED. This will allow our service to successfully start no matter what. But feels hacky, and you might not know about this LINK_REQUIRED thing until you get a surprise. I'm not sure, both variants feel somewhat flawed to me (And this is a remarkably trivial use case!). I can live with the second one, but it looks like there is still room for improvement. Thanks for your work, Regards, Nikolai
Gruesse / Regards, Marius Tomaschewski<mt@suse.de>,<mt@suse.com>
-- To unsubscribe, e-mail: wicked-devel+unsubscribe@opensuse.org To contact the owner, e-mail: wicked-devel+owner@opensuse.org