Sponsored Content
Full Discussion: find command
Top Forums UNIX for Dummies Questions & Answers find command Post 302187116 by era on Saturday 19th of April 2008 10:05:26 AM
Old 04-19-2008
grep is for looking at the contents of a file..

If all the files are in the current directory, echo *hakkinen* or ls *hakkinen* or anything *hakkinen* -- read the manual for your shell for more on wildcards.

If you want to find files in any directory (or any directory which is a subdirectory of a particular directory) the find command is the correct choice.

Code:
find /path/to/dir -name '*hakkinen*'

To search all mounted disks, use / instead of /path/to/dir

This is a very basic use case and is probably featured as an example in your local manual page for find
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

command find returned bash: /usr/bin/find: Argument list too long

Hello, I create a file touch 1201093003 fichcomp and inside a repertory (which hava a lot of files) I want to list all files created before this file : find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long but i make a filter all... (1 Reply)
Discussion started by: yacsil
1 Replies

2. Shell Programming and Scripting

Little bit weired : Find files in UNIX w/o using find or where command

Yes , I have to find a file in unix without using any find or where commands.Any pointers for the same would be very helpful as i am beginner in shell scritping and need a solution for the same. Thanks in advance. Regards Jatin Jain (10 Replies)
Discussion started by: jatin.jain
10 Replies

3. UNIX for Dummies Questions & Answers

how to find a file named vijay in a directory using find command

I need to find whether there is a file named vijay is there or not in folder named "opt" .I tried "ls *|grep vijay" but it showed permission problem. so i need to use find command (6 Replies)
Discussion started by: amirthraj_12
6 Replies

4. Shell Programming and Scripting

find: No match due to find command being argument

I am using csh and getting the error "find: No match." but I cannot figure out why. What I am trying to do is set the find command to a variable and then execute the variable as a command. I ran it through a debugger and it looks like $FIND is getting set but the find command can not actually be... (2 Replies)
Discussion started by: mst3k4l
2 Replies

5. Linux

Simplified find command to find multiple file types

Hi, I'm using the following command to find the multiple requierd file types and its working fine find . -name "*.pl" -o -name "*.pm" -o -name "*.sql" -o -name "*.so" -o -name "*.sh" -o -name "*.java" -o -name "*.class" -o -name "*.jar" -o -name "*.gz" -o -name "*.Z" -type f Though... (2 Replies)
Discussion started by: vickramshetty
2 Replies

6. Shell Programming and Scripting

what is the find command to find exact dir from the root

I want to find a dir called STOP from the root.so what is the find command. Thanks & Regards Rajkumar (1 Reply)
Discussion started by: rajkumar_g
1 Replies

7. Shell Programming and Scripting

Find, regular expression, anyway to simplify this find command?

Hello everyone, first post here, trying to learn scripting on my own and this forum as been really helpful so far. I made few little scripts working great but I m facing some problems with RE. I have a bunch of files in many subdirectories called *001.ext *002.ext OR simple *.ext or *01.ext... (7 Replies)
Discussion started by: Sekullos
7 Replies

8. Shell Programming and Scripting

How to use grep & find command to find references to a particular file

Hi all , I'm new to unix I have a checked project , there exists a file called xxx.config . now my task is to find all the files in the checked out project which references to this xxx.config file. how do i use grep or find command . (2 Replies)
Discussion started by: Gangam
2 Replies

9. Shell Programming and Scripting

Find multiple string in one file using find command

Hi, I want find multiple string in one file using find coomand. And keeping it in one variable.grep is not working. (5 Replies)
Discussion started by: vivek1489
5 Replies

10. Solaris

Is it possible to find the seek rate of the find command in Solaris?

Hello, I am running some performance based tests on Solaris, and I was wondering how fast the "seeking" rate of Solaris is, or how fast Solaris can get information about files with the "find" command. Does anyone know what 'find' command I could run to traverse through my system to see the rate... (1 Reply)
Discussion started by: bstring
1 Replies
kits(1) 						      General Commands Manual							   kits(1)

Name
       kits - generate setld format distribution kits

Syntax
       /usr/sys/dist/kits key-file input-path output-path [ subset...  ]

Description
       The  command  produces  subset images, inventories, and control files for an installation using the 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 destination  direc-
       tory into which the kit information is to be placed.

       The command produces a subset image and a .image file in the output-path directory for each subset. In the instctrl subdirectory of output-
       path, produces an inventory file and a control file. Any subset control program for the subset is transferred to output-path/instctrl.	An
       instctrl directory is created if none existed.

Arguments
       key-file       The  path  name 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.

       input-path     The path name which specifies the top of a hierarchy of files. This hierarchy contains the files which are to be kitted into
		      subsets.

       output-path    The name of the directory to be used to store the subset image and data files produced by the command.

       subset...      The names of individual subsets can be specified by optionally listing them on the command line. If they are specified, only
		      those subsets will be kitted. The 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.

Restrictions
       Any subset control programs to be provided with the kit must be located in a directory scps in the working directory where the  program	is
       invoked. If no subset control program is found for a subset, an empty one is created.

Examples
       The  following  example	shows the command used to 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 ULT400.k /var/kits/input /var/kits/output
       The next example shows the same usage, but specifies that only the ULTACCT400 subset is to be created.
	   kits ULT400.k /var/kits/input /var/kits/output ULTACCT400

Diagnostics
       kits: key-file not found
       The program was unable to find the key-file specified on the command line.

       kits: input-path not found
       The program was unable to find the specified input-path.

       kits: output-path not found
       The program was unable to find the  specified output-path.

       kits: cannot create instctrl directory.
       The program cannot create an instctrl directory under output-path.  Check that the user has write permission to output-path.

       kits: key-file format error
       One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is either missing or has a null value.

       Inventory file pathname not found
       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.

       Generating media creation information...failed.
       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.

       No such subset in key-file subset subset
       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.

       compression failed. status = status
       The  compression  option  was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the program
       once more.

Files
       temporary files.

       log of subset packaging activity

See Also
       invcutter(1), tarsets(1), stl_comp(5), stl_ctrl(5), stl_image(5), stl_key(5), stl_mi(5), stl_scp(5), setld(8)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																	   kits(1)
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy