diff options
author | Sverker Eriksson <[email protected]> | 2019-05-22 18:01:23 +0200 |
---|---|---|
committer | Sverker Eriksson <[email protected]> | 2019-05-22 18:01:23 +0200 |
commit | 55cee8416a689d3adf57fc0b20959c328f8c83bd (patch) | |
tree | 6db331d9e98973f3baccbc105300d487368a1cc4 /erts/doc/src/erlang.xml | |
parent | 90b543e2415762df46a4eb2e5b8c7bf2c318f0f3 (diff) | |
parent | 7d54af059fffd27286f6a236470a9096c09921a9 (diff) | |
download | otp-55cee8416a689d3adf57fc0b20959c328f8c83bd.tar.gz otp-55cee8416a689d3adf57fc0b20959c328f8c83bd.tar.bz2 otp-55cee8416a689d3adf57fc0b20959c328f8c83bd.zip |
Merge branch 'sverker/erts/system_monitor-doc/ERL-936' into maint
* sverker/erts/system_monitor-doc:
erts: Add some erl_nif doc clarifications
erts: Clarify erlang:system_monitor/2 semantics
Diffstat (limited to 'erts/doc/src/erlang.xml')
-rw-r--r-- | erts/doc/src/erlang.xml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index 68cde567c2..f41ed87048 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -9413,6 +9413,18 @@ Metadata = #{ pid => pid(), <p>Returns the previous system monitor settings just like <seealso marker="#system_monitor/0"> <c>erlang:system_monitor/0</c></seealso>.</p> + <p>The arguments to <c>system_monitor/2</c> specifies how all + system monitoring on the node should be done, not how it should be + changed. This means only one process at a time + (<c><anno>MonitorPid</anno></c>) can be the receiver of system monitor + messages. Also, the way to clear a specific monitor option + is to not include it in the list <c><anno>Options</anno></c>. All + system monitoring will, however, be cleared if the process identified by + <c><anno>MonitorPid</anno></c> terminates.</p> + <p>There are no special option values (like zero) to clear an option. + Some of the options have a unspecified minimum value. Lower values + will be adjusted to the minimum value. For example, it is currently not + possible to monitor all garbage collections with <c>{long_gc, 0}</c>.</p> <note> <p>If a monitoring process gets so large that it itself starts to cause system monitor messages when garbage |