Clarify waitup arguments.

diff --git a/dhcpcd.8.in b/dhcpcd.8.in
index 900544f62fd7786ff61f9bfcbb8c88396e72d3db..d8b6781f97f16abf64bb4ee2f242c7fb0c6304af 100644 (file)
--- a/dhcpcd.8.in
+++ b/dhcpcd.8.in
@@ -422,6 +422,12 @@ then exits before doing any configuration.
 Wait for an address to be assigned before forking to the background.
 4 means wait for an IPv4 address to be assigned.
 6 means wait for an IPv6 address to be assigned.
+If no argument is given,
+.Nm
+will wait for any address protocol to be assigned.
+It is possible to wait for more than one address protocol and
+.Nm
+will only fork to the background when all waiting conditions are satisfied.
 .It Fl x , Fl Fl exit Op Ar interface
 This will signal an existing
 .Nm

diff --git a/dhcpcd.conf.5.in b/dhcpcd.conf.5.in
index e49948b24f0b41f9ea581dbaa1ebc65fb5011bfd..5594e7d73cb495474e33de6f8dd70ecb362b31f3 100644 (file)
--- a/dhcpcd.conf.5.in
+++ b/dhcpcd.conf.5.in
@@ -414,6 +414,12 @@ To work around it, try and impersonate Windows by using the MSFT vendorclassid.
 Wait for an address to be assigned before forking to the background.
 4 means wait for an IPv4 address to be assigned.
 6 means wait for an IPv6 address to be assigned.
+If no argument is given,
+.Nm
+will wait for any address protocol to be assigned.
+It is possible to wait for more than one address protocol and
+.Nm
+will only fork to the background when all waiting conditions are satisfied.
 .It Ic xidhwaddr
 Use the last four bytes of the hardware address as the DHCP xid instead
 of a randomly generated number.