|
|
Sponsored Content
Operating Systems
Linux
Red Hat
How to find the path of a command?
Post 302907954 by vamshigvk475 on Wednesday 2nd of July 2014 03:50:44 PM
07-02-2014
How to find the path of a command?
Last edited by Scott; 07-02-2014 at 07:11 PM.. Reason: Please use code tags
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
When I do
find . -name "*.txt" -size +0 -exec ls {} \;
I get something like
./lpi_stdout.txt
./lpi_stderr.txt
What would I need to do or pipe it into to strip off those first two characters so I just get
lpi_stdout.txt
lpi_stderr.txt
?
Thanks for the help! (1 Reply)
Discussion started by: LordJezo
1 Replies
2. UNIX for Dummies Questions & Answers
What is the command to find the path of a file if we know the file name and the root directory where the file resides..
For eg. if a file abc.dat resides in /home/mydir/myfiles/. I am looking for a command which will be fired from / directory, takes abc.dat as input and display the path of... (3 Replies)
Discussion started by: abhilashnair
3 Replies
3. UNIX for Dummies Questions & Answers
I'm trying to autogenerate a PATH variable from the output of a find command as follows:
PATH=`find $dir -name "*.jar" | sed 's/$/:/'`
The output looks similar like this if I echo it:
PATH=/path/to/1.jar:
/path/to/2.jar:
/path/to/3.jar:
I want the path to be on one line.
I'm on... (3 Replies)
Discussion started by: rein
3 Replies
4. UNIX for Advanced & Expert Users
HI ,
I am trying to wite a script that will prompt me saying " what is path that you want to find ?". once i specify the path, the script should put this path in the find command mentioned below and execute the script:
find <path> -ctime +200 -type f -exec ls -l {} \;
for example :
... (7 Replies)
Discussion started by: bsandeep_80
7 Replies
5. UNIX for Dummies Questions & Answers
i understand by using the pwd command we get the present working directory.
which command is used to find absolute path from home directory to root..
What is absolute path to your and root user's home directory.:confused::confused::confused: (2 Replies)
Discussion started by: shaziafathima
2 Replies
6. Shell Programming and Scripting
I have the following FTP embedded in a Ksh script on AIX 5.3
ftp -n <<WHATEVER
open 10.101.26.218
user hcistats *******
ascii
put $thupdatefile
put $thcollectfile
quit
WHATEVER
Here is what my script returns:
... (3 Replies)
Discussion started by: troym72
3 Replies
7. Shell Programming and Scripting
When this command is issued from a directory other than where the file is located it works fine:
find /db2/D01/log_archive/ -name "S0002166.LOG" -type f
/db2/D01/log_archive/db2d01/D01/NODE0000/C0000000/S0002166.LOG
When I change -name to -newer, it doesn't work. Find only searches the current... (5 Replies)
Discussion started by: fletchdb2
5 Replies
8. UNIX for Dummies Questions & Answers
I have a script like this running under OS X 10.8. The problem arises when the find command encounters a space in the path name. I need the "dir" variable as I'll be extending the script to more general use.
#!/bin/bash
CFS=$IFS
IFS=$(echo)
set dir = "/Users/apta/Library/Mail\... (3 Replies)
Discussion started by: apta
3 Replies
9. Red Hat
Hi Folks,
I want to run the below command and to exclude the specific path like /var/test/support/... . How to achieve using the below command
find / -type f \( –perm –4000 –o –perm –2000 \) –print
-Siva
Please do not use FONT tags inside CODE tags. And, there is usually no reason to... (2 Replies)
Discussion started by: gsiva
2 Replies
10. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
LEARN ABOUT OSF1
kits
kits(1) General Commands Manual kits(1) NAME
kits - Generates setld format distribution kits SYNOPSIS
/usr/bin/kits key-file input-path output-path [subset...] OPERANDS
The pathname of the manufacturing key file which describes the product to be kitted. Unless optional subset arguments are specified, all subsets listed in the descriptor section of the key-file are kitted. The pathname which specifies the top of a hierarchy of files. This hierarchy contains the files which are to be kitted into subsets. The name of the directory to be used to store the subset image and data files produced by the command. The names of individual subsets can be specified by optionally listing them on the command line. If they are specified, only those subsets are kitted. The kits program assumes that all other subsets for the product have been kitted and that their images are in the directory specified by output-path. The key file specified must contain descriptors for each of the optional named subsets. DESCRIPTION
The kits command produces subset images, inventories, and control files for an installation using the setld command. You need to know the key file which describes the product to be built, a hierarchy from which the component files to be kitted are to be taken, and a destina- tion directory into which the kit information is to be placed. In the output-path directory, the kits command produces a subset image file for each subset and a product_code.image file listing all the kit's subsets. In the instctrl subdirectory of output-path, kits produces an inventory file and a control file. The optional subset con- trol program for any subset in the kit is transferred to output-path/instctrl. An instctrl directory is created if none existed. RESTRICTIONS
Any subset control programs to be provided with the kit must be located in a directory named scps in the working directory where the kits program is invoked. If no subset control program is found for a subset, an empty one is created. ERRORS
The kits program was unable to find the key-file specified on the command line. The kits program was unable to find the specified input- path. The kits program was unable to find the specified output-path. The kits program cannot create an instctrl directory under output- path. Check that the user has write permission to output-path. One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is either missing or has a null value. The master inventory file pathname specified in the MI entry of the key-file cannot be found. Verify that the pathname is accessible from the current directory. There are no records in the master inventory file for a subset which is being kitted. Check the master inventory file for correctness of content and format. A subset name specified on the command line does not have a descriptor line in the key-file. Check the spelling of the subset name on the command line. Check the contents of the key-file. The compression option was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the kits program again. EXAMPLES
Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results in /var/kits/output. kits OAT100.k /var/kits/input /var/kits/output Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results in /var/kits/output, but create only the OATDCB100 subset. kits OAT100.k /var/kits/input /var/kits/output OATDCB100 FILES
Log of subset packaging activity SEE ALSO
invcutter(1), newinv(1), tarsets(1), setld(8) stl_comp(4), stl_ctrl(4), stl_image(4), stl_key(4), stl_mi(4), stl_scp(4) Guide to Preparing Product Kits kits(1)