10-25-2011
Thanks, that worked
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
We currently use the below basic scripts to output details that the business requires for our AIX and Sun servers. I have been asked to produce the same sort of script to be used for our NCR MP-RAS UNIX and OS/2 UNIX servers but am not formilar with these forms of Unix. Would greatly... (0 Replies)
Discussion started by: kmuir
0 Replies
2. UNIX for Advanced & Expert Users
Hello All
I have always had a question about find and replace in Vi. As this uses Vi, sed, and RegEx I never knew how or where to post the question but I thought I would give it a shot here. Say I have a text file filled with the following:
Sue, your IP address is 192.168.1.10 which is... (4 Replies)
Discussion started by: NoSalt
4 Replies
3. UNIX for Dummies Questions & Answers
i feel weird with this 2 command
find /tmp/*test* -user `whoami` -mtime +1 -type f -exec rm -f {}\;
find /tmp/*test* -user `whoami` -mtime +1 -type f -exec ls -lrt {}\;
the first one return correct which only delete those filename that consist *test* where second command it listed all the... (12 Replies)
Discussion started by: lsy
12 Replies
4. UNIX Desktop Questions & Answers
Hello,
I would like to ask you, how to match directory names. I need to find only directories, which are created only from numbers and doesn't include any letters.
I used command
find $AC_WORKDIR/work_archive/test/$dirs_years -maxdepth 1 -name \\* -print
If I have dirs like
12... (3 Replies)
Discussion started by: satin1321
3 Replies
5. Shell Programming and Scripting
Platform: AIX 6.1/ksh
Question1.
I want to grep for the string "CUSTOM_PKMS" in all the files in server except those files with extensions .dbf , .ctl and .dmp
I started running the following command but it is taking too long because there are lots of .dbf , .ctl and .dmp files in this... (6 Replies)
Discussion started by: John K
6 Replies
6. Shell Programming and Scripting
Hello Friends,
I have a problem about a little script,
when i run the following two lines one by one on CLI then they work well:
/usr/bin/mkdir `perl -e 'use POSIX qw(strftime); print strftime "%Y-%m-%d",localtime(time() - 30*24*60*60);'`
find . -type f -name "fuseesb.log.*" -mtime 30... (5 Replies)
Discussion started by: EAGL€
5 Replies
7. AIX
Hello every one.
I know little to nothing about AIX. Recently I have been assigned to an AIX project.
For some reason or another the find command is hanging the server.
Well it does not hand server per say, it just freezes my terminal session.
after running find, I waited up to 40 min and... (3 Replies)
Discussion started by: busi386
3 Replies
8. UNIX for Dummies Questions & Answers
Hello all,
I need some help and education creating a script.
Basically I have a file with a list of numbers..
2125554444
2124445555
I need to put them into a format that looks like this....
UQ-V8.1,2125554444,hdaudio
UQ-V8.1,2124445555,hdaudio
Any help would be greatly... (6 Replies)
Discussion started by: jay11789
6 Replies
9. UNIX for Beginners Questions & Answers
Hello Forum,
I'm using the following command to find all inactive kernels installed on my RHEL server:
$ rpm -qa | grep '^kernel-' |grep -vE `uname -r`
but the result is in two lines:
kernel-3.10.0-1062.1.1.el7.x86_64
kernel-3.10.0-1062.el7.x86_64
Is there a one line command I can... (3 Replies)
Discussion started by: greavette
3 Replies
10. Shell Programming and Scripting
Hello Forum,
We have two bootstraps of Chef in our environment which are identified by colour:
/var/chef/cache/cookbooks/bootstrap_cookbooks_version_green
and
/var/chef/cache/cookbooks/bootstrap_cookbooks_version_red
I'm attempting to identify which version is installed based on the name... (11 Replies)
Discussion started by: greavette
11 Replies
LEARN ABOUT FREEBSD
whereis
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