Logging agent
The 'Log::Agent' module provides an abstract layer for logging and tracing, which is independent from the actual method used to physically perform those activities. It acts as an agent (hence the name) that collects the requests and delegates processing to a sublayer: the logging driver.
The 'Log::Agent' module is meant to be used in all reusable components, since they cannot know in advance how the application which ends up using them will perform its logging activities: either by emitting messages on stdout and errors on stderr, or by directing messages to logfiles, or by using syslog(3).
The logging interface is common for all the logging drivers, and is therefore the result of a compromise between many logging schemes: any information given at this level must be either handled by all drivers, or may be ignored depending on the application's final choice.
- Sources inherited from project devel:languages:perl
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:Tomcat42/perl-Log-Agent && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| Log-Agent-1.003.tar.gz | 0000055841 54.5 KB | |
| cpanspec.yml | 0000000469 469 Bytes | |
| perl-Log-Agent.changes | 0000001627 1.59 KB | |
| perl-Log-Agent.spec | 0000002727 2.66 KB |
Revision 7 (latest revision is 8)
Stephan Kulow (coolo)
committed
(revision 7)
- updated to 2.001003
see /usr/share/doc/packages/perl-Function-Parameters/Changes
2.001003 2017-11-11
- Fix threaded initialization issue better. This is the same issue
that was fixed in 2.001002, but now we use PL_op_mutex instead of
PL_check_mutex. This has the advantage of also being thread-safe on
v5.14.
2.001002 2017-11-09
- Fix crash when Function::Parameters is loaded at runtime by
multiple threads (a stack overflow due to infinite recursion).
This is arguably a core bug (#132413). The current workaround
employed by Function::Parameters slightly abuses an internal perl
mutex meant for something else (protecting op checkers), but it
fixes the issue on perls v5.16 .. v5.26.
v5.14 doesn't have this API yet, so the workaround is not thread
safe there. It is technically possible to still run into this issue
if two threads initialize Function::Parameters at the exact same
moment (I haven't managed to reproduce this yet, so hopefully it's
unlikely in practice).
It is possible to completely avoid the problem on all versions of
perl and Function::Parameters by making sure the module is loaded
before the first thread is created.
Comments 0