On Mon, May 11, 2020 at 09:11:32PM -0500, Chris Adams wrote:
> Once upon a time, Zbigniew Jędrzejewski-Szmek said:
> > Yep. There's also /run/systemd/resolve/resolv.conf, where systemd-resolved
> > always exposes a list (with the limitations described above).
>
> I wasn't aware of that file... to
Once upon a time, Zbigniew Jędrzejewski-Szmek said:
> Yep. There's also /run/systemd/resolve/resolv.conf, where systemd-resolved
> always exposes a list (with the limitations described above).
I wasn't aware of that file... to me, that's a rather obscure location
(and I didn't find it mentioned a
On Mon, May 11, 2020 at 08:58:46PM +0200, Marius Schwarz wrote:
> Am 11.05.20 um 20:35 schrieb Zbigniew Jędrzejewski-Szmek:
> >
> > Is /run/systemd/resolve/resolv.conf good enough? Would a comment in
> > /etc/resolv.conf pointing the user to that file help?
> >
> Why not using a symlink from new to
Am 11.05.20 um 20:35 schrieb Zbigniew Jędrzejewski-Szmek:
>
> Is /run/systemd/resolve/resolv.conf good enough? Would a comment in
> /etc/resolv.conf pointing the user to that file help?
>
Why not using a symlink from new to old resolve.conf?
This way old app will keep working and admins also do no
On Mon, May 11, 2020 at 01:02:56PM -0500, Chris Adams wrote:
> Once upon a time, Igor Raits said:
> > * #2381 F33 System-Wide Change: systemd-resolved (ignatenkobrain,
> > 15:10:20)
> > * AGREED: APPROVED (+4, ±5, -0) (ignatenkobrain, 15:18:40)
> > * AGREED: APPROVED (+5, ±4, -0) (ignaten
Once upon a time, Igor Raits said:
> * #2381 F33 System-Wide Change: systemd-resolved (ignatenkobrain,
> 15:10:20)
> * AGREED: APPROVED (+4, ±5, -0) (ignatenkobrain, 15:18:40)
> * AGREED: APPROVED (+5, ±4, -0) (ignatenkobrain, 15:20:51)
> * AGREED: APPROVED (+6, ±3, -0) (ignatenkobrain
