Need to select files larger than 500Mb from servers
I need help modifying these two scripts to do the following:
- print files in (MB) instead of (KB)
- only select files larger than 500MB -> these will be mailed out daily
- Select all files regardless of size all in (MB) -> these will be mailed out once a week
this is what i have so far and it is now working well...help will be appreciated.
Moderator's Comments:
Please use CODE tags as required by forum rules!
Last edited by RudiC; 05-29-2018 at 12:51 PM..
Reason: Added CODE tags.
hi all,
i am looking for ways to make ftp efficient by tuning the parameters
currently,
tcp_max_buf is 1 MB
tcp_xmit_hiwat is 48 KB
say to transmit multiple 2 gb files from unix server to mainframe sys,
will increasing the window size or the send buffer size of the current TCP/IP... (6 Replies)
Hello,
I'm using CentOS 5.3, and I connect to a VPN in order to work. The problem is that I'm constantly accessing things on the local network and the remote network. But once I'm connected to the VPN I can't access local addresses by name, I have to use the ip-address.
What I'd like is to... (4 Replies)
Hi the following c-code utilizing the 'read()' man 2 read method cant read in files larger that 2gig.
Hi I've found a strange problem on ubuntu64bit, that limits the data you are allowed to allocate on a 64bit platform using the c function 'read()'
The following program wont allow to allocate... (14 Replies)
Hi,
Does anyone know if it is possible to tar files larger than 2GB? The reason being is they want me to dump a single file (which is around 20GB) to a tape drive and they will restore it on a Solaris box. I know the tar have a limitation of 2GB so I am thinking of a way how to overcome this.... (11 Replies)
I use du -sk command to find the size of the directory but when i use the result of 'du -sk' into if statement its throwing error.. Could u solve with this..? (14 Replies)
Hello Unix Gurus,
I am new to Unix so need some help on this.
I am using the following commands:
1) mv -f Inputpath/*. outputpath
2) cp Inputpath/*. outputpath
3) rm -rf somepath/*
4) Find Inputpath/*.
Now I get the following error with... (18 Replies)
My unzip command doesn't work for files that are greater than 4GB. Consider my file name is unzip -p -a filename.zip, the command doesn't work since the size of the file is larger. I need to know the corresponding 7z command for the same. This is my Unix shell script program:
if
then
... (14 Replies)
I need to backup my database but the files are very large and the TAR command will not let me. I searched aids and found that I could do something with the mknod, COMPRESS and TAR command using them together. I appreciate your help. (10 Replies)
Hi,
I have one large files of 100000 rows with header column.
Eg:
Emp Code, Emp Name
101,xxx
102,YYY
103,zzz
...
...
I want to split the files into smaller files with only 30000 rows each..File 1,2 and 3 must have 30000 rows and file 4 must contain 10000 rows.
But the column... (1 Reply)
I am new at developing EXPECT scripts. I'm trying to create a script that will automatically connect to a several UNIX (sun solaris and HPUX) database server via FTP and pull the sizes of the listener/alert log files from specified server directory on the remote machines.
1. I want the script... (7 Replies)
Discussion started by: mikebantor
7 Replies
LEARN ABOUT SUSE
apache::testtrace
Apache::TestTrace(3) User Contributed Perl Documentation Apache::TestTrace(3)NAME
Apache::TestTrace - Helper output generation functions
SYNOPSIS
use Apache::TestTrace;
debug "foo bar";
info_sub "missed it";
error_mark "something is wrong";
# test sub that exercises all the tracing functions
sub test {
print $Apache::TestTrace::LogFH
"TraceLevel: $Apache::TestTrace::Level
";
$_->($_,[1..3],$_) for qw(emerg alert crit error
warning notice info debug todo);
print $Apache::TestTrace::LogFH "
"
};
# demo the trace subs using default setting
test();
{
# override the default trace level with 'crit'
local $Apache::TestTrace::Level = 'crit';
# now only 'crit' and higher levels will do tracing lower level
test();
}
{
# set the trace level to 'debug'
local $Apache::TestTrace::Level = 'debug';
# now only 'debug' and higher levels will do tracing lower level
test();
}
{
open OUT, ">/tmp/foo" or die $!;
# override the default Log filehandle
local $Apache::TestTrace::LogFH = *OUT;
# now the traces will go into a new filehandle
test();
close OUT;
}
# override tracing level via -trace opt
% t/TEST -trace=debug
# override tracing level via env var
% env APACHE_TEST_TRACE_LEVEL=debug t/TEST
DESCRIPTION
This module exports a number of functions that make it easier generating various diagnostics messages in your programs in a consistent way
and saves some keystrokes as it handles the new lines and sends the messages to STDERR for you.
This module provides the same trace methods as syslog(3)'s log levels. Listed from low level to high level: emerg(), alert(), crit(),
error(), warning(), notice(), info(), debug(). The only different function is warning(), since warn is already taken by Perl.
The module provides another trace function called todo() which is useful for todo items. It has the same level as debug (the highest).
There are two more variants of each of these functions. If the _mark suffix is appended (e.g., error_mark) the trace will start with the
filename and the line number the function was called from. If the _sub suffix is appended (e.g., error_info) the trace will start with the
name of the subroutine the function was called from.
If you have "Term::ANSIColor" installed the diagnostic messages will be colorized, otherwise a special for each function prefix will be
used.
If "Data::Dumper" is installed and you pass a reference to a variable to any of these functions, the variable will be dumped with
"Data::Dumper::Dumper()".
Functions whose level is above the level set in $Apache::TestTrace::Level become NOPs. For example if the level is set to alert, only
alert() and emerg() functions will generate the output. The default setting of this variable is warning. Other valid values are: emerg,
alert, crit, error, warning, notice, info, debug.
Another way to affect the trace level is to set $ENV{APACHE_TEST_TRACE_LEVEL}, which takes effect if $Apache::TestTrace::Level is not set.
So an explicit setting of $Apache::TestTrace::Level always takes precedence.
By default all the output generated by these functions goes to STDERR. You can override the default filehandler by overriding
$Apache::TestTrace::LogFH with a new filehandler.
When you override this package's global variables, think about localizing your local settings, so it won't affect other modules using this
module in the same run.
TODO
o provide an option to disable the coloring altogether via some flag
or import()
AUTHOR
Stas Bekman with contributions from Doug MacEachern
perl v5.12.1 2007-12-31 Apache::TestTrace(3)