10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hello, all
I have googled internet, read the man page of Find, searched this forum, but still could not figure out how.
My current directory is:
little@wenwen:~$ pwd
/home/little
little@wenwen:~$
I want to use find command to list the files in my current directory, how should i write... (3 Replies)
Discussion started by: littlewenwen
3 Replies
2. Shell Programming and Scripting
I need to search the file using strings "Request Type" , " Request Method" , "Response Type" and by using result set find the xml tags and convert into a single line?. below are the scenarios.
Cat test
Nov 10, 2012 5:17:53 AM
INFO: Request Type
Line 1.... (5 Replies)
Discussion started by: laknar
5 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
I am trying to delete file (with a mtime older than 2 days) from the current directory ONLY using:
find . -daystart -maxdepth 1 -mtime 2 -exec rm {} \;
but this doesn't seem to work it is still find files in subdirectories which I don't want to delete.
Please can anyone offer... (2 Replies)
Discussion started by: daveu7
2 Replies
4. Shell Programming and Scripting
Dear All,
i want to search particular string and want to replance next line value.
following is the test file.
search string is
tmp,???
,10:1 "???" may contain any 3 character it should remain the same and next line replace with ,10:50
tmp,123 --- if match tmp,??? then... (3 Replies)
Discussion started by: arvindng
3 Replies
5. Shell Programming and Scripting
hello All,
i have to two files package.today and package.yesterday , the extension of the files says what day the file belongs to .
contents of the file change little bit everyday .
i am taking only the package and sub package from the files
awk '/^/{print $0}' Packages.today
82 ... (0 Replies)
Discussion started by: posner
0 Replies
6. Shell Programming and Scripting
Hello,
Can anybody help me to correct my sed syntax to find the string and print previous two lines and current line and next one line.
i am using string as "testing"
netstat -v | sed -n -e '/test/{x;2!p;g;$!N;p;D;}' -e h
i am able to get the previous line current line next line but... (1 Reply)
Discussion started by: nmadhuhb
1 Replies
7. Shell Programming and Scripting
Hi,
I have a command "get_data" with some parameters in few *.text files of a directory. I want to first find those files that contain this command and then append the following parameter to the end of the command.
example of an entry in the file :-
get_data -x -m50 /etc/web/getid
this... (1 Reply)
Discussion started by: PrasannaKS
1 Replies
8. Shell Programming and Scripting
Hi,
I want to grep the line which has 'data11'.then from that line, i need to trace back and find out the immediate line which has the same timestamp of that grepped line.
for eg:
log file:
-----------
Process - data
Process - datavalue - 2345
Process - data
Process - data
Process... (9 Replies)
Discussion started by: Sharmila_P
9 Replies
9. Shell Programming and Scripting
Hi All,
I have a file that I need to be able to find a pattern match on a line, search that line for a text pattern, and replace that text.
An example of 4 lines in my file is:
1. MatchText_randomNumberOfText moreData ReplaceMe moreData
2. MatchText_randomNumberOfText moreData moreData... (4 Replies)
Discussion started by: Crypto
4 Replies
10. UNIX for Dummies Questions & Answers
Hi,
By default FIND command searches for matching files in all the subdirectories within the specified path.
Is there a way to restrict FIND command's search path to only the specified directory and NOT TO scan its subdirectories.
Any help would be more than appreciated.
Thanks and Regards (2 Replies)
Discussion started by: super_duper_guy
2 Replies
WHEREIS(1) BSD General Commands Manual WHEREIS(1)
NAME
whereis -- locate programs
SYNOPSIS
whereis [-abmqsux] [-BMS dir ... -f] program ...
DESCRIPTION
The whereis utility checks the standard binary, manual page, and source directories for the specified programs, printing out the paths of any
it finds. The supplied program names are first stripped of leading path name components, any single trailing extension added by gzip(1),
compress(1), or bzip2(1), and the leading 's.' or trailing ',v' from a source code control system.
The default path searched is the string returned by the sysctl(8) utility for the ``user.cs_path'' string, with /usr/libexec and the current
user's $PATH appended. Manual pages are searched by default along the $MANPATH. Program sources are located in a list of known standard
places, including all the subdirectories of /usr/src and /usr/ports.
The following options are available:
-B Specify directories to search for binaries. Requires the -f option.
-M Specify directories to search for manual pages. Requires the -f option.
-S Specify directories to search for program sources. Requires the -f option.
-a Report all matches instead of only the first of each requested type.
-b Search for binaries.
-f Delimits the list of directories after the -B, -M, or -S options, and indicates the beginning of the program list.
-m Search for manual pages.
-q (``quiet''). Suppress the output of the utility name in front of the normal output line. This can become handy for use in a back-
quote substitution of a shell command line, see EXAMPLES.
-s Search for source directories.
-u Search for ``unusual'' entries. A file is said to be unusual if it does not have at least one entry of each requested type. Only
the name of the unusual entry is printed.
-x Do not use ``expensive'' tools when searching for source directories. Normally, after unsuccessfully searching all the first-level
subdirectories of the source directory list, whereis will ask locate(1) to find the entry on its behalf. Since this can take much
longer, it can be turned off with -x.
EXAMPLES
The following finds all utilities under /usr/bin that do not have documentation:
whereis -m -u /usr/bin/*
Change to the source code directory of ls(1):
cd `whereis -sq ls`
SEE ALSO
find(1), locate(1), man(1), which(1), sysctl(8)
HISTORY
The whereis utility appeared in 3.0BSD. This version re-implements the historical functionality that was lost in 4.4BSD.
AUTHORS
This implementation of the whereis command was written by Jorg Wunsch.
BUGS
This re-implementation of the whereis utility is not bug-for-bug compatible with historical versions. It is believed to be compatible with
the version that was shipping with FreeBSD 2.2 through FreeBSD 4.5 though.
The whereis utility can report some unrelated source entries when the -a option is specified.
BSD
August 22, 2002 BSD