02-15-2015
Thanks, the explanation in your manpage is clearer than the one in mine.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am looking for all the header files (*.h).. which as per documentation of the UNIX system shouldbe there.
I am using
find / -name *.h -print
But it does't give anything.
My question is under what condition the "find" condition will fail to find the file?
What is the work around.
... (4 Replies)
Discussion started by: rraajjiibb
4 Replies
2. Windows & DOS: Issues & Discussions
I am working on a batch script where a filter is placed on a directory, and the files that come out of that filter have to be copied into another directory. More specifically, I am trying to set the results of a FIND command to a variable, so that I may access this variable / file later.
The... (2 Replies)
Discussion started by: JP Favara
2 Replies
3. Shell Programming and Scripting
Hi
I'm working on solaris and I'm trying to run a script. The part listed here does not work properly, the result of the find command is not in the output
file /tmp/result
(I've checked the find command , executing the shell with sh -x , it seems correct). It seems like I've lost the standard... (4 Replies)
Discussion started by: frenchwill
4 Replies
4. UNIX for Dummies Questions & Answers
Hi!
Could you please explain why the result order isn't in reverse time order as it is requestet by "xargs ls -ltr" command (ksh shell)? There are about 5000 files in dir.
$ find . -name "*201010*" -print |xargs ls -ltr |tail
-rw-r--r-- 1 oracle oinstall 54326 Nov 25 20:32... (2 Replies)
Discussion started by: laki47
2 Replies
5. Shell Programming and Scripting
Hi,
I have following codes which looks ok:
$ string1="123456789 abc2"
$ string2="abc"
$ position_of_string2=`expr index "$string1" "$string2"`
$ echo $position_of_string2
$
11however, when string2="abc2", it gives me the following result:
$ string1="123456789 abc2"
$... (5 Replies)
Discussion started by: littlewenwen
5 Replies
6. Shell Programming and Scripting
Hi
I run the below command to find and delete *.xml files 90 or more days old.
find . -type f -name '*.xml' -mtime +90 -exec rm {} \;
find: stat() error ./Hello/2014_EMPTY.xml: No such file or directory
./Hello/2014_EMPTY_8011.xml: No such file or directory
.....
....
If the file... (10 Replies)
Discussion started by: mohtashims
10 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a main folder 'home'. Lets say there is a folder 'bin' under 'home'. I want to check the list of files under subdirectories present under the /bin directory created in the last 24 hours.
I am using the following find command under home/bin directory:
find . -mtime -1 -print
... (3 Replies)
Discussion started by: DJose
3 Replies
8. Shell Programming and Scripting
Given this bit of script:
retprd=$1
find ${extrnllogdir} -name "*.log" -mtime +$retprd -exec ls -l {} \; >> $logfile
produces this (with 'set -x')
++ find /xfers/oracle/dw/data -name '*.log' -mtime +60 -exec ls -l '{}' ';'
find: /xfers/oracle/dw/data/cron: Permission denied
Where is he... (5 Replies)
Discussion started by: edstevens
5 Replies
9. Shell Programming and Scripting
I want to remove any files that are older than 2 days from a directory. It deletes those files. Then it comes back with a message it is a directory. What am I doing wrong here?
+ find /mydir -mtime +2 -exec rm -f '{}' ';'
rm: /mydir is a directory (2 Replies)
Discussion started by: jtamminen
2 Replies
10. Shell Programming and Scripting
Hello.
From a script, a command for a test is use :
find /home/user_install -maxdepth 1 -type f -newer /tmp/000_skel_file_deb ! -newer /tmp/000_skel_file_end -name '.bashrc' -o -name '.profile' -o -name '.gtkrc-2.0' -o -name '.i18n' -o -name '.inputrc'
Tha command... (3 Replies)
Discussion started by: jcdole
3 Replies
LEARN ABOUT SUSE
log::message::handlers
Log::Message::Handlers(3pm) Perl Programmers Reference Guide Log::Message::Handlers(3pm)
NAME
Log::Message::Handlers - Message handlers for Log::Message
SYNOPSIS
# Implicitly used by Log::Message to serve as handlers for
# Log::Message::Item objects
# Create your own file with a package called
# Log::Message::Handlers to add to the existing ones, or to even
# overwrite them
$item->carp;
$item->trace;
DESCRIPTION
Log::Message::Handlers provides handlers for Log::Message::Item objects. The handler corresponding to the level (see Log::Message::Item
manpage for an explanation about levels) will be called automatically upon storing the error.
Handlers may also explicitly be called on an Log::Message::Item object if one so desires (see the Log::Message manpage on how to retrieve
the Item objects).
Default Handlers
log
Will simply log the error on the stack, and do nothing special
carp
Will carp (see the Carp manpage) with the error, and add the timestamp of when it occurred.
croak
Will croak (see the Carp manpage) with the error, and add the timestamp of when it occurred.
cluck
Will cluck (see the Carp manpage) with the error, and add the timestamp of when it occurred.
confess
Will confess (see the Carp manpage) with the error, and add the timestamp of when it occurred
die
Will simply die with the error message of the item
warn
Will simply warn with the error message of the item
trace
Will provide a traceback of this error item back to the first one that occurrent, clucking with every item as it comes across it.
Custom Handlers
If you wish to provide your own handlers, you can simply do the following:
o Create a file that holds a package by the name of "Log::Message::Handlers"
o Create subroutines with the same name as the levels you wish to handle in the Log::Message module (see the Log::Message manpage for
explanation on levels)
o Require that file in your program, or add it in your configuration (see the Log::Message::Config manpage for explanation on how to use
a config file)
And that is it, the handler will now be available to handle messages for you.
The arguments a handler may receive are those specified by the "extra" key, when storing the message. See the Log::Message manpage for
details on the arguments.
SEE ALSO
Log::Message, Log::Message::Item, Log::Message::Config
AUTHOR
This module by Jos Boumans <kane@cpan.org>.
Acknowledgements
Thanks to Ann Barcomb for her suggestions.
COPYRIGHT
This module is copyright (c) 2002 Jos Boumans <kane@cpan.org>. All rights reserved.
This library is free software; you may redistribute and/or modify it under the same terms as Perl itself.
perl v5.12.1 2010-04-26 Log::Message::Handlers(3pm)