From b075fbda0ad0a711344011fb365b00acd5b64760 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= Date: Wed, 3 Apr 2019 13:20:37 +0200 Subject: Fix broken links A multitude of broken links were found when a bug was fixed in the link checker. --- erts/doc/src/alt_disco.xml | 2 +- erts/doc/src/communication.xml | 2 +- erts/doc/src/crash_dump.xml | 2 +- erts/doc/src/erl_driver.xml | 24 ++++++++++++------------ erts/doc/src/erl_ext_dist.xml | 6 +++--- erts/doc/src/erl_nif.xml | 4 ++-- erts/doc/src/erlang.xml | 6 ++++-- erts/doc/src/notes.xml | 10 ++++------ 8 files changed, 28 insertions(+), 28 deletions(-) (limited to 'erts') diff --git a/erts/doc/src/alt_disco.xml b/erts/doc/src/alt_disco.xml index d04221b9b3..148d6f549e 100644 --- a/erts/doc/src/alt_disco.xml +++ b/erts/doc/src/alt_disco.xml @@ -63,7 +63,7 @@ EPMD module. However, instead of communicating with EPMD you can connect to any service to find out connection details of other nodes. A discovery module is enabled - by setting -epmd_module + by setting -epmd_module when starting erlang. The discovery module must implement the following callbacks:

diff --git a/erts/doc/src/communication.xml b/erts/doc/src/communication.xml index 7e18a73aa8..251b52dc65 100644 --- a/erts/doc/src/communication.xml +++ b/erts/doc/src/communication.xml @@ -64,7 +64,7 @@ a synchronous communication operation consists of two asynchronous signals; one request signal and one reply signal. An example of such a synchronous communication is a call to - + erlang:process_info/2 when the first argument is not self(). The caller sends an asynchronous signal requesting information, and then diff --git a/erts/doc/src/crash_dump.xml b/erts/doc/src/crash_dump.xml index a9aeb1888c..33d0903622 100644 --- a/erts/doc/src/crash_dump.xml +++ b/erts/doc/src/crash_dump.xml @@ -290,7 +290,7 @@ Slogan: <reason> Memory Information

Under the tag =memory is shown information similar to what can be obtainted on a living node with - + erlang:memory().

diff --git a/erts/doc/src/erl_driver.xml b/erts/doc/src/erl_driver.xml index 58678f2393..3e2d3bb447 100644 --- a/erts/doc/src/erl_driver.xml +++ b/erts/doc/src/erl_driver.xml @@ -230,7 +230,7 @@

With these functions, the driver sends data back to the emulator. The data is received as messages by the port owner process, see - + erlang:open_port/2. The vector function and the function taking a driver binary are faster, as they avoid copying the data buffer. There is also a fast way of sending @@ -1154,27 +1154,27 @@ r = driver_async(myPort, &myKey, myData, myFunc); ]]> start - Called from + Called from erlang:open_port/2. output - Called from + Called from erlang:send/2 and - + erlang:port_command/2. outputv - Called from + Called from erlang:send/2 and - + erlang:port_command/2. control - Called from + Called from erlang:port_control/3. call - Called from + Called from erlang:port_call/3.

Notice that this function is not thread-safe, not @@ -2305,7 +2305,7 @@ r = driver_async(myPort, &myKey, myData, myFunc); ]]> *value_size has been set to the buffer size needed.

This function reads the emulated environment used by - os:getenv/1 and not + os:getenv/1 and not the environment used by libc's getenv(3) or similar. Drivers that require that these are in sync will need to do so themselves, but keep in mind that they are segregated for a reason; @@ -2656,7 +2656,7 @@ erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]

This function modifies the emulated environment used by - os:putenv/2 and not + os:putenv/2 and not the environment used by libc's putenv(3) or similar. Drivers that require that these are in sync will need to do so themselves, but keep in mind that they are segregated for a reason; @@ -2849,7 +2849,7 @@ erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0]

Sets the os_pid seen when doing - + erlang:port_info/2 on this port.

port is the port handle of the port (driver instance) to set the pid on. pidis the pid to set.

@@ -3204,7 +3204,7 @@ erl_drv_output_term(driver_mk_port(drvport), spec, sizeof(spec) / sizeof(spec[0] control driver entry function will return data to the port owner process. (The control function is called from - + erlang:port_control/3.)

Currently there are only two meaningful values for flags: 0 means that data is returned in a list, diff --git a/erts/doc/src/erl_ext_dist.xml b/erts/doc/src/erl_ext_dist.xml index 4721747097..6b7a6db943 100644 --- a/erts/doc/src/erl_ext_dist.xml +++ b/erts/doc/src/erl_ext_dist.xml @@ -399,7 +399,7 @@ REFERENCE_EXT

Encodes a reference object (an object generated with - erlang:make_ref/0). + erlang:make_ref/0). The Node term is an encoded atom, that is, ATOM_UTF8_EXT, SMALL_ATOM_UTF8_EXT, or @@ -437,7 +437,7 @@ PORT_EXT

Encodes a port object (obtained from - + erlang:open_port/2). The ID is a node-specific identifier for a local port. Port operations are not allowed across node boundaries. @@ -467,7 +467,7 @@ PID_EXT

Encodes a process identifier object (obtained from - erlang:spawn/3 or + erlang:spawn/3 or friends). The ID and Creation fields works just like in REFERENCE_EXT, while the Serial field is used to improve safety. diff --git a/erts/doc/src/erl_nif.xml b/erts/doc/src/erl_nif.xml index cf1994887a..c0be715678 100644 --- a/erts/doc/src/erl_nif.xml +++ b/erts/doc/src/erl_nif.xml @@ -546,8 +546,8 @@ int writeiovec(ErlNifEnv *env, ERL_NIF_TERM term, ERL_NIF_TERM *tail,

Many operations communicating with a process executing a dirty NIF can, however, complete while it executes the dirty NIF. For example, retrieving information about it through - - erlang:process_info, setting its group leader, + + process_info, setting its group leader, register/unregister its name, and so on.

Termination of a process executing a dirty NIF can only be completed up to a certain point while it executes the dirty NIF. diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index 0d94f83493..2b444ccf01 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -126,7 +126,7 @@ instance.

One can get an approximation of the native time unit by calling - + erlang:convert_time_unit(1, second, native). The result equals the number of whole native time units per second. If @@ -4663,6 +4663,7 @@ RealSystem = system + MissedSystem Information about the memory size of a port. +

Bytes is the total number of bytes allocated for this port by the runtime system. The port itself can have allocated memory that is not @@ -5387,6 +5388,7 @@ RealSystem = system + MissedSystem {memory, Size} +

Size is the size in bytes of the process. This includes call stack, heap, and internal structures.

@@ -6676,7 +6678,7 @@ lists:map( async Async threads are used by various linked-in drivers (mainly the file drivers) do offload non-CPU intensive work. See - erl +A for more details. + erl +A for more details. aux Takes care of any work that is not specifically assigned to a scheduler. diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml index 7c5a8aefad..13cd4129ac 100644 --- a/erts/doc/src/notes.xml +++ b/erts/doc/src/notes.xml @@ -8363,8 +8363,7 @@ Erlang/OTP has been ported to the realtime operating system OSE. The port supports both smp and non-smp emulator. For details around the port and how to started - see the User's Guide in the ose application.

+ see the User's Guide in the ose application.

Note that not all parts of Erlang/OTP has been ported.

@@ -9470,9 +9469,9 @@ fix_alloc allocator, a different strategy for management of fix blocks will be used. The information returned from erlang:system_info({allocator, + marker="erlang#system_info_allocator_tuple">erlang:system_info({allocator, A}), and erlang:system_info({allocator_sizes, + marker="erlang#system_info_allocator_sizes">erlang:system_info({allocator_sizes, A}) will be slightly different when this feature has been enabled. An mbcs_pool tuple will be present giving information about abandoned carriers, @@ -10281,8 +10280,7 @@ information about signal ordering guarantees, see the chapter on communication in - the ERTS user's guide. The +n command line flag of + the ERTS user's guide. The +n command line flag of erl(1) can be helpful when trying to find signaling order bugs in Erlang code that have been exposed by these -- cgit v1.2.3