12-24-2019
If you don't mind Google scanning and "machine reading" all your email, that's an OK approach.
Of course, that depends on your requirements for confidentiality and your risk management model.
Lot's of folks out there get "in trouble" using third party email providers.
I guess confidentiality and privacy are not really major concerns for your organization.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How can I determine if the data collection rate is 1 Hz on Solaris? (0 Replies)
Discussion started by: laila63
0 Replies
2. 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
3. UNIX for Dummies Questions & Answers
Would appreciate some help, system was displaying an error regarding the kernal when a "sar" was run, after a reboot we get "WARNING user login limit exceeded by 1 user". We have plenty of licences. any ideas? (1 Reply)
Discussion started by: nchrocc
1 Replies
4. UNIX and Linux Applications
Does anyone know what's Sendmail outgoing email rate? e.g. 1000 outgoing email per minutes. If so, can we modify it?
Thanks.
:) (1 Reply)
Discussion started by: sunmagic2003
1 Replies
5. Shell Programming and Scripting
Hi,
I need help in writing unix script for checking space of some directories on the system and also send an email when it reaches the threshold limit.
I have written the followng code;
#!/bin/ksh
ADMIN="me@somewhere.com"
# set alert level 80% is default
THRESHOLD=80
df | grep -E... (5 Replies)
Discussion started by: jmathew99
5 Replies
6. AIX
Hello,
How can i tell ifthe ratio between fr and sr is ok?
is fr/sr ratio of 0.9 acceptable?
thanks. (1 Reply)
Discussion started by: LiorAmitai
1 Replies
7. Solaris
Hi all, I'm using to Solaris machine. When I run a simple script this messenger come out:"limit: stacksize: Can't remove limit". Any one know the way to resolve this problem without reboot the machine?
Thanks in advance. (3 Replies)
Discussion started by: Diabolist9
3 Replies
8. 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
9. Shell Programming and Scripting
Deal all,
I have a directory called
I want to know how many MBs are transferred to it every 2 hours.
How can I do this?
Any ideas?
I have a simple idea but I can't translate it into shell script, the idea is:
1- get the size of the folder now, using
2- then get the size of the... (4 Replies)
Discussion started by: Mohannad
4 Replies
10. UNIX for Advanced & Expert Users
I have D-Link Router DSL-2730U that support busybox OS and iptables version 1.4.0
I managed successfully to block the host for being connect to the internet using the following command
block by ip address
iptables -I FORWARD -d 192.168.1.6 -j DROP
Or By mac source
iptables -I... (0 Replies)
Discussion started by: iLinux85
0 Replies
LEARN ABOUT DEBIAN
log::log4perl::appender::limit
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)