- Timestamp:
- 02/05/2022 01:54:13 AM (2 years ago)
- Branches:
- 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 21dd2f0, 3e09569
- Parents:
- 1f8c0b9
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter09/networkd.xml
r1f8c0b9 r0a75d62 185 185 (ex: a <command>resolvconf</command> program other than the one 186 186 provided by systemd), the <command>systemd-resolved</command> service 187 should not be used.</para></note> 187 should not be used.</para> 188 189 <para>To disable systemd-resolved, issue the following command:</para> 190 191 <screen role="nodump"><userinput>systemctl disable systemd-resolved</userinput></screen></note> 188 192 189 193 <para>When using <command>systemd-resolved</command> for DNS 190 194 configuration, it creates the file 191 <filename>/run/systemd/resolve/resolv.conf</filename>. Create a 195 <filename>/run/systemd/resolve/resolv.conf</filename>.</para> 196 <!--Create a 192 197 symlink in <filename>/etc</filename> to use the generated file:</para> 193 198 194 199 <screen><userinput>ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen> 195 200 At least in systemd-250, this file gets created on first bootup. 201 --> 196 202 </sect3> 197 203
Note:
See TracChangeset
for help on using the changeset viewer.