Skip to content

Commit 809ed9c

Browse files
committed
resolvconf.8: resolvconf -I should be called during early boot
It's not mandatory, but does put the system into a saner state if no resolv.conf gets added for a while and DNS is expected to work.
1 parent 539659c commit 809ed9c

1 file changed

Lines changed: 5 additions & 9 deletions

File tree

resolvconf.8.in

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
2323
.\" SUCH DAMAGE.
2424
.\"
25-
.Dd May 13, 2025
25+
.Dd June 24, 2025
2626
.Dt RESOLVCONF 8
2727
.Os
2828
.Sh NAME
@@ -253,14 +253,10 @@ system startup:
253253
.It Fl I
254254
Initialise the state directory
255255
.Pa @VARDIR@ .
256-
This only needs to be called if the initial system boot sequence does not
257-
automatically clean it out; for example the state directory is moved
258-
somewhere other than
259-
.Pa /var/run .
260-
If used, it should only be called once as early in the system boot sequence
261-
as possible and before
262-
.Nm
263-
is used to add entries.
256+
This should be called after the base state directory has either been
257+
cleaned out or mounted as a memory backed filesystem during the
258+
initial boot sequence before any daemon has the chance to call
259+
.Nm .
264260
.It Fl R
265261
Echo the command used to restart a service.
266262
.It Fl r Ar service

0 commit comments

Comments
 (0)