Tracking Message Buffer


 
Thread Tools Search this Thread
Operating Systems Linux Tracking Message Buffer
# 1  
Old 05-19-2004
Tracking Message Buffer

Is there a way to track the message buffer to see which messages are being sent and the time that it was sent between messages?

thanks much!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Tracking Process to a particular

I've tried to see what I can find on my own but I'm coming up with goose eggs. Basically I was wondering if there was a way of querying the scheduler (or something similar) to track a process back to a particular CPU it's executing on at the time of the command. ps has a "cpu" output option but... (1 Reply)
Discussion started by: thmnetwork
1 Replies

2. AIX

Tracking Root commands

Hi All How can track what commands are entered by the Root user. Is there a log besides using the history command that lists all commands entered for a period of time. thanks:o (6 Replies)
Discussion started by: pashan
6 Replies

3. IP Networking

netfilter connection tracking

hi, i'm using tcpreplay to send a traffic trace to my wireless interface (the trace is been captured by the same interface). It seems as netfilter can't trace connections. Is it possible? (0 Replies)
Discussion started by: littleboyblu
0 Replies

4. Programming

How to limit max no of message in a posix message queue

Hii can anyone pls tell how to limit the max no of message in a posix message queue. I have made changes in proc/sys/fs/mqueue/msg_max But still whenever i try to read the value of max. message in the queue using attr.mq_curmsgs (where struct mq_attr attr) its giving the default value as 10.... (0 Replies)
Discussion started by: mohit3884
0 Replies

5. Shell Programming and Scripting

server load tracking

I have written a script which checks server load and emails me. I am running into the error: ./load_alert.sh: line 8: ; then printf "WARNING - cpu load high in xyz server" fi (2 Replies)
Discussion started by: vsmurali
2 Replies

6. UNIX for Advanced & Expert Users

Tracking down the problem

Is there a way to track down what process is sending to a certain port? I have some thing pounding the network with requests to a multicast IP that doesn't exist. I have shut down all comms related processes and yet it is still there. Need a way to track the port or IP back to the process. Thanks... (3 Replies)
Discussion started by: mattmanuel
3 Replies

7. UNIX for Advanced & Expert Users

Tracking user

dear all, I'm facing problem that is i have noticed from few days back that some body is deleting and making changes in the file from developement server where i'm working(in unix) so i want to track that who is using the server, what performancr they are doing and each every thing which r... (5 Replies)
Discussion started by: panknil
5 Replies

8. UNIX for Advanced & Expert Users

tracking user action

Hi, we are using solaris8. we have some files disappear. I would like to know how to track who and when the files was remove ??? thanks, (7 Replies)
Discussion started by: xitrum
7 Replies

9. UNIX for Advanced & Expert Users

Command Tracking

Hi, OS: Solaris9, SPARC Is there any way I can track the commands run by users from the shell prompt? Example: Somebody is deleting files from the system. Who it is is a mystery. That person obviously does not use bash prompt so there is no history. Is there anyway I can find out who... (5 Replies)
Discussion started by: mahatma
5 Replies

10. UNIX for Dummies Questions & Answers

sendmail message body buffer limit?

when sending the contents of a ascii file to the body of an email then sending it off. it seems sendmail is breaking up the lines with a "!" thus ruining the data. Has this ever happened to anyone? i am guessing there is a line buffer limit in either the mail command or in sendmail itself. ... (3 Replies)
Discussion started by: Optimus_P
3 Replies
Login or Register to Ask a Question
Appender::Buffer(3)					User Contributed Perl Documentation				       Appender::Buffer(3)

NAME
Log::Log4perl::Appender::Buffer - Buffering Appender SYNOPSIS
use Log::Log4perl qw(:easy); my $conf = qq( log4perl.category = DEBUG, Buffer # Regular Screen Appender log4perl.appender.Screen = Log::Log4perl::Appender::Screen log4perl.appender.Screen.stdout = 1 log4perl.appender.Screen.layout = PatternLayout log4perl.appender.Screen.layout.ConversionPattern = %d %p %c %m %n # Buffering appender, using the appender above as outlet log4perl.appender.Buffer = Log::Log4perl::Appender::Buffer log4perl.appender.Buffer.appender = Screen log4perl.appender.Buffer.trigger_level = ERROR ); Log::Log4perl->init($conf); DEBUG("This message gets buffered."); INFO("This message gets buffered also."); # Time passes. Nothing happens. But then ... print "It's GO time!!! "; ERROR("This message triggers a buffer flush."); DESCRIPTION
"Log::Log4perl::Appender::Buffer" takes these arguments: "appender" Specifies the name of the appender it buffers messages for. The appender specified must be defined somewhere in the configuration file, not necessarily before the definition of "Log::Log4perl::Appender::Buffer". "max_messages" Specifies the maximum number of messages the appender will hold in its ring buffer. "max_messages" is optional. By default, "Log::Log4perl::Appender::Buffer" will not limit the number of messages buffered. This might be undesirable in long-running processes accumulating lots of messages before a flush happens. If "max_messages" is set to a numeric value, "Log::Log4perl::Appender::Buffer" will displace old messages in its buffer to make room if the buffer is full. "trigger_level" If trigger_level is set to one of Log4perl's levels (see Log::Log4perl::Level), a "trigger" function will be defined internally to flush the buffer if a message with a priority of $level or higher comes along. This is just a convenience function. Defining log4perl.appender.Buffer.trigger_level = ERROR is equivalent to creating a trigger function like log4perl.appender.Buffer.trigger = sub { my($self, $params) = @_; return $params->{log4p_level} >= $Log::Log4perl::Level::ERROR; } See the next section for defining generic trigger functions. "trigger" "trigger" holds a reference to a subroutine, which "Log::Log4perl::Appender::Buffer" will call on every incoming message with the same parameters as the appender's "log()" method: my($self, $params) = @_; $params references a hash containing the message priority (key "l4p_level"), the message category (key "l4p_category") and the content of the message (key "message"). If the subroutine returns 1, it will trigger a flush of buffered messages. Shortcut DEVELOPMENT NOTES
"Log::Log4perl::Appender::Buffer" is a composite appender. Unlike other appenders, it doesn't log any messages, it just passes them on to its attached sub-appender. For this reason, it doesn't need a layout (contrary to regular appenders). If it defines none, messages are passed on unaltered. Custom filters are also applied to the composite appender only. They are not applied to the sub-appender. Same applies to appender thresholds. This behaviour might change in the future. COPYRIGHT AND LICENSE
Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.1 2010-02-16 Appender::Buffer(3)