Home
last modified time | relevance | path

Searched refs:logging (Results 1 – 25 of 67) sorted by relevance

123

/linux-3.4.99/Documentation/device-mapper/
Ddm-log.txt3 The device-mapper logging code is used by some of the device-mapper
13 There is a generic logging interface that the device-mapper RAID
14 implementations use to perform logging operations (see
16 logging implementations are available and provide different
28 logging state survives reboots/crashes.
41 logging requests to userspace, where a daemon receives and processes the
/linux-3.4.99/Documentation/networking/
Dnetconsole.txt12 problem where disk logging fails and serial consoles are impractical.
32 tgt-port port for logging agent (6666)
33 tgt-ip IP address for logging agent
34 tgt-macaddr ethernet MAC address for logging agent (broadcast)
44 It also supports logging to multiple remote agents by specifying
61 remote logging targets to be dynamically added, removed, or have their
73 To add a remote logging target (target names can be arbitrary):
130 TIP: in case the remote logging agent is on a separate LAN subnet than
140 NOTE: if you find that the remote logging agent is not receiving or
153 enable the logging of even the most critical kernel bugs. It works
/linux-3.4.99/kernel/debug/kdb/
Dkdb_io.c556 int logging, saved_loglevel = 0; in vkdb_printf() local
592 diag = kdbgetintenv("LOGGING", &logging); in vkdb_printf()
594 logging = 0; in vkdb_printf()
711 if (logging) { in vkdb_printf()
783 if (logging) in vkdb_printf()
837 if (logging) in vkdb_printf()
/linux-3.4.99/Documentation/filesystems/
Dxfs-delayed-logging-design.txt4 Introduction to Re-logging in XFS
7 XFS logging is a combination of logical and physical logging. Some objects,
21 "re-logging". Conceptually, this is quite simple - all it requires is that any
90 The key thing to note about the asynchronous logging combined with the
104 is the fundamental goal of delayed logging.
113 Delayed logging is the name we've given to keeping and tracking transactional
122 One of the key changes that delayed logging makes to the operation of the
128 crash is much greater than for the existing logging mechanism.
137 It should be noted that delayed logging is not an innovative new concept that
145 The fundamental requirements for delayed logging in XFS are simple:
[all …]
Drelay.txt81 tarball) provides a couple of high-level logging functions to the
124 users should make sure that all logging to the channel has
419 relay_write() or __relay_write(). relay_write() is the main logging
421 used if you might be logging from interrupt context. If you know
422 you'll never be logging from interrupt context, you can use
426 value in the fast logging path anyway, and that they'll always succeed
469 within the kernel application, such as enabling/disabling logging to
/linux-3.4.99/include/trace/events/
Djbd2.h148 __field( unsigned long, logging )
161 __entry->logging = stats->rs_logging;
174 jiffies_to_msecs(__entry->logging),
/linux-3.4.99/Documentation/isdn/
DREADME.hfc-pci6 When the echo logging feature is used the number of available B-channels
19 This enables the echo mode. If Hex logging is activated the isdnctrlx
/linux-3.4.99/fs/ocfs2/
DKconfig60 bool "OCFS2 logging support"
64 The ocfs2 filesystem has an extensive logging system. The system
/linux-3.4.99/drivers/scsi/mpt2sas/
DKconfig64 bool "LSI MPT Fusion logging facility"
67 This turns on a logging facility.
/linux-3.4.99/Documentation/arm/
D00-INDEX38 - SWP/SWPB emulation handler/logging description
/linux-3.4.99/drivers/message/fusion/
DKconfig111 bool "Fusion MPT logging facility"
113 This turns on a logging facility that can be used to debug a number
/linux-3.4.99/arch/powerpc/platforms/pseries/
DKconfig83 bool "Enable extra debug logging in platforms/pseries"
120 kernel buffer. Saying Y here will enable logging these events,
/linux-3.4.99/net/sunrpc/
DKconfig49 logging of different aspects of the kernel RPC activity.
/linux-3.4.99/Documentation/s390/
DCommonIO9 Enable logging of debug information in case of ccw device timeouts.
120 The level of logging can be changed to be more or less verbose by piping to
/linux-3.4.99/drivers/acpi/apei/
DKconfig29 bool "APEI PCIe AER logging/recovering support"
/linux-3.4.99/Documentation/power/regulator/
Dmachine.txt57 for use in logging and other diagnostic output. Normally the name
/linux-3.4.99/Documentation/
Dramoops.txt11 crashes. It works by logging oopses and panics in a circular buffer. Ramoops
Dldm.txt74 "Windows LDM extra logging" CONFIG_LDM_DEBUG
/linux-3.4.99/fs/cifs/
DKconfig44 allow optional logging of slow responses to dmesg (depending on the
123 the cifs module and can cause additional logging of debug
/linux-3.4.99/include/linux/
Dwanrouter.h138 unsigned char logging; /* Control connection logging */ member
/linux-3.4.99/net/bridge/netfilter/
DKconfig201 logging daemon using netlink multicast sockets. This differs
212 messages through the netfilter logging API, which can use
/linux-3.4.99/Documentation/dvb/
Dcontributors.txt17 for CyberLogin for Linux which allows logging onto EON
/linux-3.4.99/Documentation/scsi/
Dscsi-parameters.txt103 scsi_logging_level= [SCSI] a bit mask of logging levels
/linux-3.4.99/drivers/scsi/
DKconfig223 bool "SCSI logging facility"
226 This turns on a logging facility that can be used to debug a number
229 If you say Y here, no logging output will appear by default, but you
230 can enable logging by saying Y to "/proc file system support" and
235 where <bitmask> is a four byte value representing the logging type
236 and logging level for each type of logging selected.
238 There are a number of logging types and you can find them in the
239 source at <file:drivers/scsi/scsi_logging.h>. The logging levels
241 the logging for each logging type.
246 logging turned off.
/linux-3.4.99/net/ipv4/netfilter/
DKconfig136 any iptables table. The packet is passed to a userspace logging
140 The appropriate userspace logging daemon (ulogd) may be obtained from

123