Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: find problem
Top Forums Shell Programming and Scripting find problem Post 302398859 by methyl on Thursday 25th of February 2010 08:31:43 PM
Old 02-25-2010
Not clear what you are trying to achieve.

Which directories do you want to search for big files? (Full pathname please).

Or.

Which directories do you not want to search for big files? (Full pathname please).



Maybe by "expect" you actually mean "except". Please check the wording of your post with someone with good English.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Another Find Problem

HI All, I am having a bit of trouble using the find command in my shell (korn) script. I was hoping someone could help me. I am trying to build up a dynamic find command based on some parameters. When I execute the command I get the following error: find: incomplete statement I have... (6 Replies)
Discussion started by: sethkor
6 Replies

2. Shell Programming and Scripting

Problem with `find ...`

Hi all, Have the following snippet of code that I'm having trouble trying to work ... The snippet of code is running on our Production Server and the intent is to copy the second most recent IDE file across from the Development Server. I have the following files defined in $DEVLOC ...... (4 Replies)
Discussion started by: Cameron
4 Replies

3. Shell Programming and Scripting

problem with find

Hi, Iam having a strange problem, wandering if soneone can throw some lights. I have statement find . -maxdepth 1 -name 'File1*.tsv' -mtime +1 -print I expect the above statement to print the files older than 1 day or 24 hrs, however it doesn't work that way. When issue above command,... (2 Replies)
Discussion started by: braindrain
2 Replies

4. UNIX for Dummies Questions & Answers

Problem with find and tar

When I am doing the first command the result shows all the files, links, directories except the ones that contain the word logs find . -type f -o -type l -o -type d | grep -v logs But when I am trying to do this even the logs are getting tarred tar -cvf fdtvision.tar `find . -type f -o -type l... (2 Replies)
Discussion started by: venu_nbk
2 Replies

5. UNIX for Dummies Questions & Answers

problem with find and mtime

I am using HP-UNIX , The below command doesnt display anything although i have changed a file in the directory by toutch -t 200010101800 nfile find /tmp/transfer/ -name "*.*" -mtime +1 Any problrm with the find command i written . .Please help ??.. Thanks, Arun (4 Replies)
Discussion started by: arunkumar_mca
4 Replies

6. Shell Programming and Scripting

Find command problem

Hi All, I am using following find command to delete the records older than 7 days but getting missing conjuction error.Kindly suggest: The command is: find <complete_dir_path> \(! -name usr -prune \) -type f -name "*.txt" -mtime +6 -print | xargs rm (11 Replies)
Discussion started by: visingha
11 Replies

7. Shell Programming and Scripting

Problem with find command.

I'm trying to display the full file name (including the full path) and file size of all files whose name (excluding the path) is longer than 10 characters. I came up with find path -type f -name ".{10, }" -printf "%s %p\n", but I'm getting a "find: path: No such file or directory". What's wrong... (2 Replies)
Discussion started by: raidkridley
2 Replies

8. Shell Programming and Scripting

find problem

for index in `find /root -name *.jar | grep "/lib"`; do echo "$index"; done sometimes its throwing error saying find: paths must precede expression Usage: find some1 suggested me that : Code: for index in `find /technologies -name '*.jar' | grep "/lib"` do echo "$index"... (2 Replies)
Discussion started by: crackthehit007
2 Replies

9. Shell Programming and Scripting

Problem with find command "find: cannot open"

Hello Guys , I am trying to run below find command in one of my SH script on a HP UX machine. find /tmp -type f -name "MGCA*.log" -prune -exec rm -f {} \; 2>&1 I want this to check my tmp directory and delete MGCA log files .But below error message is printed on Promt :- find: cannot... (2 Replies)
Discussion started by: himanshu sood
2 Replies

10. Shell Programming and Scripting

Problem with find

Hello, I have trouble using the find command (I am working on Mac OSX). for i in *.pdf do if find . -name "EV" then mv "$i" E-test.pdf elif find . -name "GV" then mv "$i" G-test.pdf else mv "$i" test.pdf fi done As to the use of "$i": unfortunately, the filenames... (14 Replies)
Discussion started by: tempestas
14 Replies

LEARN ABOUT DEBIAN

rmdir

RMDIR(2)						     Linux Programmer's Manual							  RMDIR(2)

NAME

       rmdir - delete a directory

SYNOPSIS

       #include <unistd.h>

       int rmdir(const char *pathname);

DESCRIPTION

       rmdir() deletes a directory, which must be empty.

RETURN VALUE

       On success, zero is returned.  On error, -1 is returned, and errno is set appropriately.

ERRORS

       EACCES Write  access to the directory containing pathname was not allowed, or one of the directories in the path prefix of pathname did not
	      allow search permission.	(See also path_resolution(7).

       EBUSY  pathname is currently in use by the system or some process that prevents its removal.  On Linux this  means  pathname  is  currently
	      used as a mount point or is the root directory of the calling process.

       EFAULT pathname points outside your accessible address space.

       EINVAL pathname has .  as last component.

       ELOOP  Too many symbolic links were encountered in resolving pathname.

       ENAMETOOLONG
	      pathname was too long.

       ENOENT A directory component in pathname does not exist or is a dangling symbolic link.

       ENOMEM Insufficient kernel memory was available.

       ENOTDIR
	      pathname, or a component used as a directory in pathname, is not, in fact, a directory.

       ENOTEMPTY
	      pathname	contains  entries  other than . and .. ; or, pathname has ..  as its final component.  POSIX.1-2001 also allows EEXIST for
	      this condition.

       EPERM  The directory containing pathname has the sticky bit (S_ISVTX) set and the process's effective user ID is neither the user ID of the
	      file  to	be deleted nor that of the directory containing it, and the process is not privileged (Linux: does not have the CAP_FOWNER
	      capability).

       EPERM  The file system containing pathname does not support the removal of directories.

       EROFS  pathname refers to a directory on a read-only file system.

CONFORMING TO

       SVr4, 4.3BSD, POSIX.1-2001.

BUGS

       Infelicities in the protocol underlying NFS can cause the unexpected disappearance of directories which are still being used.

SEE ALSO

       rm(1), rmdir(1), chdir(2), chmod(2), mkdir(2), rename(2), unlink(2), unlinkat(2)

COLOPHON

       This page is part of release 3.44 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2008-05-08								  RMDIR(2)
All times are GMT -4. The time now is 06:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy