| Age | Commit message (Collapse) | Author |
|---|
|
OTP-14359: Add typespecs for netns and bind_to_device options
|
|
|
|
|
|
|
|
This field contains the index of all installed handlers. It is
internal and can not be altered by the user, and should therefore not
be visible.
|
|
|
|
This function earlier only added/removed the old error_logger_tty_h
report handler. Since it is mostly used for turning off logging to tty
in general, it now also checks the default logger handlers. It works
as follows:
tty(true):
* If default handler is logger_std_h of type standard_io, make sure it
has no 'error_logger_tty_false filter'.
* Else, add a new instance of logger_std_h with type standard_io with
id 'error_logger_tty_true'.
tty(false):
* Remove error_logger_tty_h report handler if it exists.
* Remove error_logger_tty_false logger handler if it exists.
* If default handler is logger_std_h of type standard_io, add a filter
named 'error_logger_tty_false', which stops all events.
|
|
These are replaced by new config handling and must not be used any
more.
|
|
|
|
Most logger configuration that was possible through
kernel application variables have been moved into a
common 'logger' application environment in kernel.
Now all the configuration possible through the logger
API can be done as sys config.
The handler started by kernel has been renamed to 'default'
instead of logger_std_h.
There is a new logger:setup_handlers/1 function that given an
application name can be used to setup handlers in other applications.
|
|
* peppe/peppe/kernel/logger_handler_fixes:
Various logger handler improvements and updated test cases
Make it possible to disable sync and drop mode
Conflicts:
lib/kernel/test/logger_disk_log_h_SUITE.erl
lib/kernel/test/logger_std_h_SUITE.erl
|
|
epmd: allow alternative to dns resolving for nodename
|
|
* siri/kernel/dont-store-incl-apps-in-env/OTP-15071:
Don't save included_applications as application environment variable
|
|
This makes it possible to create a custom integration with a
key-value store for example. The key would then point to the
actual address. You would have to write your own epmd module
to make use of that feature.
|
|
The error_logger is no longer added here.
|
|
|
|
Some networking functions accept the options netns (to switch network
namespaces) and bind_to_device (to bind to a device with
SO_BINDTODEVICE), but these functions are not annotated to accept these
options, which causes dialyzer to raise issues.
This patch applies these type specs to the options for
gen_tcp:connect/3,4, gen_tcp:listen/2, gen_udp:open/1,2, and
gen_sctp:open/0,1,2, as these are the documented functions which accept
the netns and bind_to_device options.
|
|
|
|
Fix syntactic issues in EDoc comments across some libs
|
|
* siri/logger-fix:
Change logger callback removing_handler/1 to removing_handler/2
Don't crash logger_server due to unexpected message
Add logger:update_process_metadata/1
Improve documentation of logger:set_*_config functions
Change return type from logger_formatter:format/2
Improve test of logger_disk_log_h and logger_std_h
Update logger documentation
Set single_line=true by default in logger_formatter
|
|
|
|
|
|
|
|
This used to be string() is now changed to unicode:chardata().
|
|
During application load, the included_applications key from the .app
file would earlier be duplicated as an application environment
variable. Due to this, its value could be retrieved in any of the
following ways:
application:get_key(App,included_applications).
application:get_env(App,included_applications).
It would also be included in the resulting list from the following calls:
application:get_all_key(App).
application:get_all_env(App).
This commit removes the duplication, and included_applications will no
longer be returned by application:get_env/2 or application:get_all_env/1.
The reason for this change is mainly to avoid confusion, but also to
avoid the potensial inconsistency which would occur if the environment
variable was changed during runtime by calls to
application:put_env(App,included_applications,NewInclApps).
|
|
|
|
See https://github.com/erszcz/docsh/issues/23 for an explanation
about how the files were found.
|
|
* john/kernel/add-file_int-to-release:
Add file_int.hrl to release target
|
|
Also add tests and update failing test cases
|
|
|
|
|
|
* raimo/better-TLS-distribution/OTP-14969:
Fix distro CRL test cases short vs long names
Allow check for node name
Move check ip to before SSL handshake
Check client IP from server
Parse cert primarily for host names
Open for host and node allow list
Create plug-in for distro cert nodes
Rewrite TLS dist to handle node names in certs
Improve node allowed check
|
|
* siri/kernel/logger/OTP-13295:
Add documentation of the built-in logger handlers
Catch badarg in logger:get_format_depth/0
Add chars_limit option to logger_formatter
Don't kill logger process until all other processes are dead
Set call timeout for logger_server to infinity
Update primary bootstrap
Test cuddle for logger
Update cth_log_redirect to a logger handler
Start using logger internally in kernel and stdlib
Remove error_logger process and add logger process
Add logger
|
|
|
|
|
|
|
|
This env var lookup may fail during termination, when
application_controller process has terminated before logger.
|
|
|
|
This is to avoid failing starts when running make with '-j',
i.e. maximum parallell make (or on extremely slow machines).
|
|
|
|
|
|
|
|
|
|
* Move the node name check earlier
* Check while still a list
* Export allowed check function
* Make allowed check function handle atom and list mixes
|
|
|
|
Run debug VM or config with --enable-lock-checking.
Exercise VM and then run
erts_debug:lc_graph().
to create a file "lc_graph.<pid>" in current working directory.
|
|
|
|
jhogberg/john/erts/any-term-as-seq_trace-label/OTP-14899
Lift the type restrictions on seq_trace token labels
|
|
* raimo/type-posix-0-overhaul/ERL_550/OTP-14019:
Update types for posix error codes
|
|
I have read the man pages for most socket and file operations
on recent Linux, FreeBSD, OpenBSD and Solaris 10 and noted
the possible error codes.
Which error codes that are possible for file operations have
been updated in file:posix/0. Error codes for socket operations
in inet:posix/0. The latter refers to the former so it is
a superset, assuming that e.g sendfile and AF_UNIX socket
operations could cause socket operations to return any file
error code. That is not entirely true, but could be,
especially in the future.
Added to file:posix/0 are:
ebadmsg edeadlk edeadlock eftype emultihop enobufs enolck enolink
enosr enostr enosys eopnotsupp eoverflow erange etxtbsy
Added to inet:posix/0 are all but:
exbadport exbadseq file:posix()
These are still possible according to erl_posix_str.c,
but are not in file:posix/0 nor in inet:posix/0,
and many of them are not file nor inet related, but some might be:
e2big eadv ealign ebade ebadfd ebadr ebadrpc ebadrqc
ebadslt ebfont echild echrng ecomm edirty
edom edotdot eduppkg eidrm einit eisnam
elbin el2hlt el2nsync el3hlt el3rst
elibacc elibbad elibexec elibmax elibscn elnrng
enavail enet enoano enocsi enodata enoexec
enonet enosym enotempty enotnam enotuniq
eproclim eprocunavail eprogmismatch eprogunavail
erefused eremchg eremdev eremote eremoteio
eremoterelease erpcmismatch erremote eshutdown
esrmnt esuccesss etime etoomanyrefs
euclean eunatch eusers eversion exfull
sysnotready vernotsupported ediscon enomore
ecancelled einvalidproctable einvalidprovider eproviderfailedinit
syscallfailure service_not_found type_not_found e_no_more
e_cancelled unknown
|
