diff options
Diffstat (limited to 'docs/src/guide')
| -rw-r--r-- | docs/src/guide/filesystem.rst | 2 | ||||
| -rw-r--r-- | docs/src/guide/networking.rst | 4 | ||||
| -rw-r--r-- | docs/src/guide/processes.rst | 8 | ||||
| -rw-r--r-- | docs/src/guide/utilities.rst | 2 |
4 files changed, 8 insertions, 8 deletions
diff --git a/docs/src/guide/filesystem.rst b/docs/src/guide/filesystem.rst index 63dbbe47..e89d4cd5 100644 --- a/docs/src/guide/filesystem.rst +++ b/docs/src/guide/filesystem.rst @@ -33,7 +33,7 @@ A file descriptor is obtained using int uv_fs_open(uv_loop_t* loop, uv_fs_t* req, const char* path, int flags, int mode, uv_fs_cb cb) ``flags`` and ``mode`` are standard -`Unix flags <http://man7.org/linux/man-pages/man2/open.2.html>`_. +`Unix flags <https://man7.org/linux/man-pages/man2/open.2.html>`_. libuv takes care of converting to the appropriate Windows flags. File descriptors are closed using diff --git a/docs/src/guide/networking.rst b/docs/src/guide/networking.rst index e61f8999..b2f3fc77 100644 --- a/docs/src/guide/networking.rst +++ b/docs/src/guide/networking.rst @@ -200,7 +200,7 @@ Freenode to see an example of DNS resolution. If ``uv_getaddrinfo`` returns non-zero, something went wrong in the setup and your callback won't be invoked at all. All arguments can be freed immediately after ``uv_getaddrinfo`` returns. The `hostname`, `servname` and `hints` -structures are documented in `the getaddrinfo man page <getaddrinfo>`_. The +structures are documented in `the getaddrinfo man page <getaddrinfo_>`_. The callback can be ``NULL`` in which case the function will run synchronously. In the resolver callback, you can pick any IP from the linked list of ``struct @@ -235,7 +235,7 @@ interface has multiple IPv4/IPv6 addresses, the name will be reported multiple times, with each address being reported once. .. _c-ares: https://c-ares.haxx.se -.. _getaddrinfo: https://www.kernel.org/doc/man-pages/online/pages/man3/getaddrinfo.3.html +.. _getaddrinfo: https://man7.org/linux/man-pages/man3/getaddrinfo.3.html .. _User Datagram Protocol: https://en.wikipedia.org/wiki/User_Datagram_Protocol .. _DHCP: https://tools.ietf.org/html/rfc2131 diff --git a/docs/src/guide/processes.rst b/docs/src/guide/processes.rst index a7806278..cbd8bce7 100644 --- a/docs/src/guide/processes.rst +++ b/docs/src/guide/processes.rst @@ -266,10 +266,10 @@ Domain Socket`_, or derived from `mkfifo(1)`_, or it could actually be a This is intended for the purpose of allowing multiple libuv processes to communicate with IPC. This is discussed below. -.. _pipe(7): http://man7.org/linux/man-pages/man7/pipe.7.html -.. _mkfifo(1): http://man7.org/linux/man-pages/man1/mkfifo.1.html -.. _socketpair(2): http://man7.org/linux/man-pages/man2/socketpair.2.html -.. _Unix Domain Socket: http://man7.org/linux/man-pages/man7/unix.7.html +.. _pipe(7): https://man7.org/linux/man-pages/man7/pipe.7.html +.. _mkfifo(1): https://man7.org/linux/man-pages/man1/mkfifo.1.html +.. _socketpair(2): https://man7.org/linux/man-pages/man2/socketpair.2.html +.. _Unix Domain Socket: https://man7.org/linux/man-pages/man7/unix.7.html .. _Named Pipe: https://docs.microsoft.com/en-us/windows/win32/ipc/named-pipes diff --git a/docs/src/guide/utilities.rst b/docs/src/guide/utilities.rst index a9fe56cc..a863c5ea 100644 --- a/docs/src/guide/utilities.rst +++ b/docs/src/guide/utilities.rst @@ -243,7 +243,7 @@ We let libcurl directly write the data to a file, but much more is possible if you so desire. ``start_timeout`` will be called immediately the first time by libcurl, so -things are set in motion. This simply starts a libuv `timer <Timers>`_ which +things are set in motion. This simply starts a libuv `timer <#timers>`_ which drives ``curl_multi_socket_action`` with ``CURL_SOCKET_TIMEOUT`` whenever it times out. ``curl_multi_socket_action`` is what drives libcurl, and what we call whenever sockets change state. But before we go into that, we need to poll |