Home
last modified time | relevance | path

Searched full:logging (Results 1 – 25 of 1112) sorted by relevance

12345678910>>...45

/freebsd/contrib/kyua/utils/logging/
H A Doperations_test.cpp29 #include "utils/logging/operations.hpp"
47 namespace logging = utils::logging;
55 logging::generate_log_name(fs::path("/some/dir"), "foobar")); in ATF_TEST_CASE_BODY()
58 logging::log(logging::level_info, "file", 123, "A message"); in ATF_TEST_CASE_BODY()
62 logging::generate_log_name(fs::path("/some/dir"), "foobar")); in ATF_TEST_CASE_BODY()
70 logging::log(logging::level_info, "file", 123, "A message"); in ATF_TEST_CASE_BODY()
72 logging::log(logging::level_info, "file", 123, "A message"); in ATF_TEST_CASE_BODY()
76 logging::generate_log_name(fs::path("/some/dir"), "foobar")); in ATF_TEST_CASE_BODY()
79 logging::log(logging::level_info, "file", 123, "A message"); in ATF_TEST_CASE_BODY()
83 logging::generate_log_name(fs::path("/some/dir"), "foobar")); in ATF_TEST_CASE_BODY()
[all …]
H A Doperations.cpp29 #include "utils/logging/operations.hpp"
49 namespace logging = utils::logging;
55 /// The general idea for the application-wide logging goes like this:
57 /// 1. The application starts. Logging is initialized to capture _all_ log
61 /// 2. The application offers the user a way to select the logging level and a
71 /// 5. The internal state of the logging module is updated to only capture
82 /// application. Tests should skip this call so that the logging messages go to
96 logging::level log_level;
101 /// First time recorded by the logging module.
105 std::vector< std::pair< logging::level, std::string > > backlog;
[all …]
H A Dmacros.hpp29 /// \file utils/logging/macros.hpp
30 /// Convenience macros to simplify usage of the logging library.
37 #include "utils/logging/operations.hpp"
43 #define LD(message) utils::logging::log(utils::logging::level_debug, \
50 #define LE(message) utils::logging::log(utils::logging::level_error, \
57 #define LI(message) utils::logging::log(utils::logging::level_info, \
64 #define LW(message) utils::logging::log(utils::logging::level_warning, \
H A DMakefile.am.inc33 libutils_a_SOURCES += utils/logging/macros.hpp
34 libutils_a_SOURCES += utils/logging/operations.cpp
35 libutils_a_SOURCES += utils/logging/operations.hpp
36 libutils_a_SOURCES += utils/logging/operations_fwd.hpp
39 tests_utils_loggingdir = $(pkgtestsdir)/utils/logging
41 tests_utils_logging_DATA = utils/logging/Kyuafile
44 tests_utils_logging_PROGRAMS = utils/logging/macros_test
45 utils_logging_macros_test_SOURCES = utils/logging/macros_test.cpp
49 tests_utils_logging_PROGRAMS += utils/logging/operations_test
50 utils_logging_operations_test_SOURCES = utils/logging/operations_test.cpp
H A Dmacros_test.cpp29 #include "utils/logging/macros.hpp"
38 #include "utils/logging/operations.hpp"
42 namespace logging = utils::logging;
48 logging::set_persistency("debug", fs::path("test.log")); in ATF_TEST_CASE_BODY()
64 logging::set_persistency("debug", fs::path("test.log")); in ATF_TEST_CASE_BODY()
80 logging::set_persistency("debug", fs::path("test.log")); in ATF_TEST_CASE_BODY()
96 logging::set_persistency("debug", fs::path("test.log")); in ATF_TEST_CASE_BODY()
H A Doperations.hpp29 /// \file utils/logging/operations.hpp
30 /// Stateless logging facilities.
35 #include "utils/logging/operations_fwd.hpp"
42 namespace logging { namespace
51 } // namespace logging
/freebsd/sys/dev/isci/scil/
H A Dscic_logger.h74 /** Enables/disables logging specific to the library. */
77 /** Enables/disables logging specific to the controller. */
80 /** Enables/disables logging specific to the sas port. */
83 /** Enables/disables logging specific to the SAS phy. */
86 /** Enables/disables logging specific to the SSP remote target. */
89 /** Enables/disables logging specific to the STP remote target. */
92 /** Enables/disables logging specific to the SMP remote target. */
95 /** Enables/disables logging specific to the SMP remote initiator. */
98 /** Enables/disables logging specific to the SSP IO requests. */
101 /** Enables/disables logging specific to the STP IO requests. */
[all …]
H A Dscif_logger.h74 /** Enables/disables logging specific to the library. */
77 /** Enables/disables logging specific to the controller. */
80 /** Enables/disables logging specific to the sas port. */
83 /** Enables/disables logging specific to the domain discovery process. */
86 /** Enables/disables logging specific to the remote devices. */
89 /** Enables/disables logging specific to remote device configuration. */
92 /** Enables/disables logging specific to performing task management. */
95 /** Enables/disables logging specific to SCSI to SATA command translation. */
98 /** Enables/disables logging specific to SCSI to SATA response translation. */
101 /** Enables/disables logging specific to framework initialization. */
[all …]
H A Dsci_logger.h74 /* logging for specific log objects. */
76 /** Enable/disable error level logging for the associated logger object(s). */
79 /** Enable/disable warning level logging for the associated logger object(s). */
83 * Enable/disable informative level logging for the associated logger object(s).
89 * logging for the associated log object(s).
104 * @note Logging must be enabled at compile time in the driver, otherwise
137 * @note Logging must be enabled at compile time in the driver, otherwise
156 * the log objects for which logging is enabled at the supplied level.
166 * verbosity_mask. To enable all logging, simply set all bits in
168 * @note Logging must be enabled at compile time in the driver, otherwise
[all …]
/freebsd/contrib/ntp/libntp/lib/isc/include/isc/
H A Dlog.h176 * Establish a new logging context, with default channels.
188 *\li *lctxp will point to a valid logging context if all of the necessary
190 *\li *lcfgp will point to a valid logging configuration if all of the
209 *\li It is necessary to specify the logging context the configuration
212 * the configuration is not used by the logging context until the
216 * the configuration is that of the logging context, as specified
232 *\li lctx is a valid logging context.
236 *\li *lcfgp will point to a valid logging context if all of the necessary
263 * Associate a new configuration with a logging context.
266 *\li This is thread safe. The logging context will lock a mutex
[all …]
/freebsd/sys/dev/ice/
H A Dice_fw_logging.c34 * @brief firmware logging sysctls
36 * Contains sysctls to enable and configure firmware logging debug support.
45 * SDT provider for DTrace probes related to firmware logging events
70 * ice_reconfig_fw_log - Re-program firmware logging configuration
74 * If the adminq is currently active, ask firmware to update the logging
76 * case, ice_init_hw() will re-configure firmware logging as soon as it brings
95 "Failed to reconfigure firmware logging, err %s aq_err %s\n", in ice_reconfig_fw_log()
120 "\nControl whether to enable logging during the attach phase" \
121 "\n0 - Enable firmware logging during attach phase" \
122 "\n1 - Disable firmware logging during attach phase"
[all …]
H A Dice_fwlog.c37 * cache_cfg - Cache FW logging config
116 * ice_fwlog_init - Initialize cached structures for tracking FW logging
121 * ice_init_hw(). Firmware logging will be configured based on these settings
136 * ice_aq_fwlog_set - Set FW logging configuration AQ command (0xFF30)
141 * @log_resolution: logging resolution
188 * ice_fwlog_supported - Cached for whether FW supports FW logging or not
200 * ice_fwlog_set - Set the firmware logging settings
202 * @cfg: config used to set firmware logging
205 * logging configuration. It can be called on initialization, reset, or during
208 * If the PF wishes to receive FW logging the
[all...]
/freebsd/contrib/pam-krb5/tests/data/scripts/trace/
H A Dunsupported1 # Basic test of attempting trace logging when not supported. -*- conf -*-
26 ERR trace logging requested but not supported
31 ERR trace logging requested but not supported
35 ERR trace logging requested but not supported
38 ERR trace logging requested but not supported
41 ERR trace logging requested but not supported
44 ERR trace logging requested but not supported
47 ERR trace logging requested but not supported
50 ERR trace logging requested but not supported
H A Dsupported1 # Basic test of enabling trace logging. -*- conf -*-
26 DEBUG enabled trace logging to %0
31 DEBUG enabled trace logging to %0
35 DEBUG enabled trace logging to %0
38 DEBUG enabled trace logging to %0
43 DEBUG enabled trace logging to %0
48 DEBUG enabled trace logging to %0
53 DEBUG enabled trace logging to %0
56 DEBUG enabled trace logging to %0
/freebsd/tools/bus_space/examples/
H A Dam79c900_diag.py48 import logging
119 logging.basicConfig(level=logging.DEBUG)
122 logging.debug('pcicfg=%s (%s)' % (pcicfg, dev))
127 logging.error('Not an AMD PCnet-PCI (vendor=%x, device=%x)' %
133 logging.info('enabling I/O port decoding')
138 logging.info('enabling bus mastering')
145 logging.debug('io=%s (%s)' % (io, dev))
208 logging.info('ethernet address = ' + MACFMT % mac)
219 logging.debug("DMA memory: size = %#x (TX buffers: %u, RX buffers: %u)" %
228 logging.debug("DMA memory: CPU address: %#x, device address: %#x" %
[all …]
/freebsd/crypto/openssl/doc/man3/
H A DSSL_CTX_set_keylog_callback.pod6 SSL_CTX_keylog_cb_func - logging TLS key material
19 SSL_CTX_set_keylog_callback() sets the TLS key logging callback. This callback
23 SSL_CTX_get_keylog_callback() retrieves the previously set TLS key logging
25 key logging callback, or if SSL_CTX_set_keylog_callback is called with NULL as
26 the value of cb, no logging of key material will be done.
28 The key logging callback is called with two items: the B<ssl> object associated
31 file, the key logging callback should log B<line>, followed by a newline.
H A DOSSL_CMP_log_open.pod21 - functions for logging and error reporting
51 The logging and error reporting facility described here contains
52 convenience functions for CMP-specific logging,
74 of auditing may be required. Therefore, the logging facility supports a severity
84 OSSL_CMP_log_open() initializes the CMP-specific logging facility to output
88 As long as neither if the two is used any logging output is ignored.
101 function I<log_fn> for uniformity with CMP logging if not NULL. Otherwise it
/freebsd/crypto/heimdal/lib/krb5/
H A Dkrb5_openlog.346 .Nd Heimdal logging functions
78 function creates a logging
84 logging. This name is used to lookup which destinations to use. This
86 .Li logging
97 To close a logging facility, use the
124 which just initializes a facility, but doesn't define any actual logging
129 functions. The first of these takes a string specifying a logging
131 non-standard logging you can use the
133 function, which takes a function to use when logging.
197 Each destination may optionally be prepended with a range of logging
[all …]
/freebsd/contrib/kyua/store/
H A Dwrite_transaction_test.cpp46 #include "utils/logging/operations.hpp"
54 namespace logging = utils::logging;
107 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
125 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
155 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
174 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
214 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
235 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
260 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
294 logging::set_inmemory(); in ATF_TEST_CASE_HEAD()
[all …]
/freebsd/secure/lib/libcrypto/man/man3/
H A DSSL_CTX_set_keylog_callback.365 SSL_CTX_keylog_cb_func \- logging TLS key material
78 \&\fBSSL_CTX_set_keylog_callback()\fR sets the TLS key logging callback. This callback
82 \&\fBSSL_CTX_get_keylog_callback()\fR retrieves the previously set TLS key logging
84 key logging callback, or if SSL_CTX_set_keylog_callback is called with NULL as
85 the value of cb, no logging of key material will be done.
87 The key logging callback is called with two items: the \fBssl\fR object associated
90 file, the key logging callback should log \fBline\fR, followed by a newline.
H A DOSSL_CMP_log_open.380 \&\- functions for logging and error reporting
110 The logging and error reporting facility described here contains
111 convenience functions for CMP-specific logging,
135 of auditing may be required. Therefore, the logging facility supports a severity
145 \&\fBOSSL_CMP_log_open()\fR initializes the CMP-specific logging facility to output
149 As long as neither if the two is used any logging output is ignored.
162 function \fIlog_fn\fR for uniformity with CMP logging if not NULL. Otherwise it
/freebsd/contrib/kyua/cli/
H A Dmain_test.cpp50 #include "utils/logging/macros.hpp"
51 #include "utils/logging/operations.hpp"
60 namespace logging = utils::logging;
206 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
225 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
244 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
263 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
282 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
305 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
329 logging::set_inmemory(); in ATF_TEST_CASE_BODY()
[all …]
/freebsd/contrib/llvm-project/compiler-rt/include/xray/
H A Dxray_log_interface.h11 // APIs for installing a new logging implementation.
15 /// XRay allows users to implement their own logging handlers and install them
70 /// // be logging the data anyway).
100 /// This enum defines the valid states in which the logging implementation can
143 /// This enum indicates the installation state of a logging implementation, when
144 /// associating a mode to a particular logging implementation through
153 /// A valid XRay logging implementation MUST provide all of the function
180 /// The 0-argument function call handler. XRay logging implementations MUST
183 /// logging) those MUST be installed by the installed 'log_init' handler.
201 /// This function installs a new logging implementation that XRay will use. In
[all …]
/freebsd/share/man/man9/
H A Dalq.947 .Nd Asynchronous Logging Queues
88 mechanism, known as Asynchronous Logging Queues.
96 for an Asynchronous Logging Queue.
97 The logging facility runs in a separate kernel thread, which services
133 function creates a new variable length asynchronous logging queue.
136 argument is the name of the file to open for logging.
257 function will close the asynchronous logging queue
373 Each asynchronous logging queue is protected by a spin mutex.
425 Asynchronous Logging Queues (ALQ) facility first appeared in
/freebsd/crypto/krb5/src/plugins/kdb/db2/libdb2/man/
H A Ddb_txn.393 access methods) is that write-ahead logging is provided by
95 to record both before- and after-image logging.
118 Default locking and logging protocols are provided only if the
122 parameter must indicate both a logging mode and locking mode specified by
134 Provide redo-only logging (not currently implemented).
137 Provide undo-only logging (not currently implemented).
140 Provide undo/redo write-ahead logging.
183 If logging is enabled, a commit log record is written and flushed to disk.
188 If logging is enabled, the log is played backwards and any recovery

12345678910>>...45