10 More Discussions You Might Find Interesting
1. Solaris
Hello All,
I am having an issue with ellipse environment,
Subscribing ellipse version /opt/mincom/ellipse/bs037__ora_cics_svr
.profile: ulimit: exceeds allowable limit ,
prj -l ellsupp
#ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192... (22 Replies)
Discussion started by: Revathi2089
22 Replies
2. UNIX and Linux Applications
Just had a migration from Autosys 4.5 to R11.3.
After the migration to R11.3, Autosys jobs have been failing when the log file reaches a size of 800 MB.
This did not happen before the migration, when Autosys 4.5 was used.
Is there a way to configure the file size limit/cap in Autosys... (1 Reply)
Discussion started by: kimo222
1 Replies
3. Solaris
I have BIND 9.8.1-P1 cache only DNS server running in Solaris 10. I have upgraded the same from 9.6.1 to 9.8.1-P1. Now i am facing "file descriptor exceeds limit (4096/4096)" error frequently on the server.
Please help me on this issue! (1 Reply)
Discussion started by: sandeep.tk
1 Replies
4. Shell Programming and Scripting
How can i remove a file using shell script when its size exceeds 10MB. Given that file is located in different location to the shell script where it is running? (4 Replies)
Discussion started by: vel4ever
4 Replies
5. UNIX for Dummies Questions & Answers
Hi all.
I am trying to write a script that renames a logfile if it exceeds roughly 1 MB.
My find command is:
find some_logfile -type f -size +20000
Now I want to do my processing if it finds a file or not...
How can I go about this? The $? is 0 if it finds a file or not.
All... (4 Replies)
Discussion started by: jamie_collins
4 Replies
6. Shell Programming and Scripting
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (6 Replies)
Discussion started by: dewaraja
6 Replies
7. UNIX for Advanced & Expert Users
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies
8. Linux
Hi,
I'm using Linux 2.6 cross compiled for a embedded powerpc.
Earlier we were using busybox syslogd for logging the messages, but as the flexibilty is less, we decided to move to standard syslog.
Now I want to limit the size of the log file (/var/log/messages) to 128K.
I couldn't find... (4 Replies)
Discussion started by: jockey007
4 Replies
9. Shell Programming and Scripting
Hi EveryOne
We run CICS Sofware on our AIX Machine...
When ever some Process or Transaction loops it Takes heavy process Usage..
Is there a way that i can Get a alert message or a Message Thrown on to screen when ever a process named "cicsas" uses more that 20%... fo CPU..
I was... (4 Replies)
Discussion started by: pbsrinivas
4 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I am trying to write a script to Count Files in a directory located on a remote server and send an email Notification if it exceeds a limit. The code given below doesnot check the condition and sends the mail everytime irrespective of the condition. I have put this script in the cron. Can... (10 Replies)
Discussion started by: amitsayshii
10 Replies
Appender::Limit(3pm) User Contributed Perl Documentation Appender::Limit(3pm)
NAME
Log::Log4perl::Appender::Limit - Limit message delivery via block period
SYNOPSIS
use Log::Log4perl qw(:easy);
my $conf = qq(
log4perl.category = WARN, Limiter
# Email appender
log4perl.appender.Mailer = Log::Dispatch::Email::MailSend
log4perl.appender.Mailer.to = drone@pageme.com
log4perl.appender.Mailer.subject = Something's broken!
log4perl.appender.Mailer.buffered = 0
log4perl.appender.Mailer.layout = PatternLayout
log4perl.appender.Mailer.layout.ConversionPattern=%d %m %n
# Limiting appender, using the email appender above
log4perl.appender.Limiter = Log::Log4perl::Appender::Limit
log4perl.appender.Limiter.appender = Mailer
log4perl.appender.Limiter.block_period = 3600
);
Log::Log4perl->init($conf);
WARN("This message will be sent immediately");
WARN("This message will be delayed by one hour.");
sleep(3601);
WARN("This message plus the last one will be sent now");
DESCRIPTION
"appender"
Specifies the name of the appender used by the limiter. The appender specified must be defined somewhere in the configuration file, not
necessarily before the definition of "Log::Log4perl::Appender::Limit".
"block_period"
Period in seconds between delivery of messages. If messages arrive in between, they will be either saved (if "accumulate" is set to a
true value) or discarded (if "accumulate" isn't set).
"persistent"
File name in which "Log::Log4perl::Appender::Limit" persistently stores delivery times. If omitted, the appender will have no
recollection of what happened when the program restarts.
"max_until_flushed"
Maximum number of accumulated messages. If exceeded, the appender flushes all messages, regardless if the interval set in
"block_period" has passed or not. Don't mix with "max_until_discarded".
"max_until_discarded"
Maximum number of accumulated messages. If exceeded, the appender will simply discard additional messages, waiting for "block_period"
to expire to flush all accumulated messages. Don't mix with "max_until_flushed".
If the appender attached to "Limit" uses "PatternLayout" with a timestamp specifier, you will notice that the message timestamps are
reflecting the original log event, not the time of the message rendering in the attached appender. Major trickery has been applied to
accomplish this (Cough!).
DEVELOPMENT NOTES
"Log::Log4perl::Appender::Limit" 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.10.1 2010-07-21 Appender::Limit(3pm)
