<p dir="ltr"><br>
On 7 Dec 2015 1:49 p.m., "Christopher Larson" <<a href="mailto:kergoth@gmail.com">kergoth@gmail.com</a>> wrote:<br>
><br>
><br>
> On Tue, Nov 17, 2015 at 8:49 PM, Dan McGregor <<a href="mailto:danismostlikely@gmail.com">danismostlikely@gmail.com</a>> wrote:<br>
>><br>
>> On 12 Nov 2015 5:41 p.m., "Christopher Larson" <<a href="mailto:kergoth@gmail.com">kergoth@gmail.com</a>> wrote:<br>
>> ><br>
>> > From: Christopher Larson <<a href="mailto:chris_larson@mentor.com">chris_larson@mentor.com</a>><br>
>> ><br>
>> > We don't need nss-myhostname on systemd systems, because systemd already<br>
>> > provides myhostname, but we weren't configuring nsswitch to use it. Being able<br>
>> > to resolve the hostname is useful for a number of different applications, so<br>
>> > enable it using the same postinst/prerm bits which are in nss-myhostname.<br>
>><br>
>> I have this and a similar change for resolved in an append at work. Would others be interested in that too?<br>
><br>
><br>
> I'm sure there are folks that would find that interesting. I'm sure not everyone uses resolved, but I'm sure we want it to work well for folks taht do want to use it.<br>
></p>
<p dir="ltr">Cool. I'll post my change. nss_resolve can be used unconditionally if it's there. If resolved isn't running it falls back to nss_dns.</p>