I think I forgot a pipe. No wonder it was puzzling you.
Code:
# Find and print all directories in .../PROD-* beginning with [0-9a-f]
find /Production/ST/st*/Outbound/Prod/PROD-* -type d -name '[0-9a-f]*' -print -name '*' -prune |
# Read lines like /Production/ST/.../bcfa0dbbcf17f28c768d1d34da6b48a4 into DIR, one-by-one
while read DIR
do
# We feed that whole directory into another find, telling it to look
# for files. It prints them one by one, piped into xargs,
# which uses them as arguments for rm.
find "${DIR}/PGP" -type f -mtime +2 | xargs -d '\n' echo rm
# Remove these directories only if they're empty
rmdir "${DIR}/PGP" && rmdir "${DIR}"
# the rmdir's will cause some error messages when they fail, redirect that to /dev/null
done 2> /dev/null
If that didn't answer your question you'll need to ask about something specific.
Quote:
so in my case do I have to give it as 0-9,a-z as it could be anything between 0-9 and a-z as the first letter of the folder.
I don't think so, those look like hex: binary numbers encoded as ASCII digits 0-9 and a-f.
Quote:
is there any restriction on the # of directories I can search using this wildcard?
There's no limit on find -name '*', no, because it can process them one-by-one. When you expand * inside the shell itself, it has to find all of them at once, before find is even run, potentially running out of room.
Quote:
also won't the rmdir "${DIR}" delete the full structure? I just need only till the 32 char folder deleted and the rest should be intact.
"rmdir /path/to/folder" only removes 'folder'. And it won't even do that unless it's empty. So I try to remove /Production/ST/st*/Outbound/Prod/PROD-*/bcfa0dbbcf17f28c768d1d34da6b48a4/PGP, and if that succeeds, I try to remove /Production/ST/st*/Outbound/Prod/PROD-*/bcfa0dbbcf17f28c768d1d34da6b48a4 itself.
And as I said, don't remove the echo until you're sure it does what you want.
I'm trying to figure out how to build a small shell script that will find old .shtml files in every /tgp/ directory on the server and delete them if they are older than 10 days...
The structure of the paths are like this:
/home/domains/www.domain2.com/tgp/
/home/domains/www.domain3.com/tgp/... (1 Reply)
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)
The following command works fine in my cshell script:
set Deliverables = `find . -name "eliverables" -print`
The following command does not work:
set LASFiles = `find . -name "*." -print`
In the first example, when tested in an if statement, the script will continue whether a... (3 Replies)
Hi i have a requirement to search for all files in a directory.
the files will start as file1_*,file2_*,file3_*
where the wild card character is a timestamp. so on a particular day i may get files like
file1_1103120042
file1_1102010345
file2_1101093423
file3_1103120042... (3 Replies)
Hi ,
I am looking for a command to change directory in FTP server with wildcard specified. Basically this is what i am trying.
localserver# ftp remoteserver
ftp> ls
41000_42000
42000_43000
ftp> cd 41*
550 CWD failed. '41*' : no such file or directory.
Could anyone please let me know... (6 Replies)
i have this find command on my script as:
for i in `find $vdir -name "$vfile" -mtime +$pday`
the problem with this code is that the sub-directories are included on the search. how do i restrict the search to confine only on the current directory and ignore the sub-directories. please advise.... (7 Replies)
I'm sure this is by design, but using something like
for f in dir/*
do echo $f
done
produces unexpected (to me) results if run against an empty directory. I'd have expected it to not execute the loop, but it actually calls it with f set to 'dir/*'.
Now I know that I'm trying to protect... (2 Replies)
so i have a script that i do not want copies of that script to be roaming around. i want that script to be in only one location on the filesystem, and whoever wants to use it should just link to it.
any idea on how to exit from a script if it is detected that the running version is a copy and... (5 Replies)
How can i tweak the below find command to exclude directory/s -> "/tmp/logs"
find . -type f \( ! -name "*.log*" ! -name "*.jar*" \) -printNote: -path option/argument does not work with the version of find that i have.
bash-3.2$ uname -a
SunOS mymac 5.10 Generic_150400-26 sun4v sparc sun4v (7 Replies)
HI there,
I am trying to find and replace with wildcard with
data
chr1 69511 69511 A G 1/1:0,34:791,78,0:78:34 0/1:55,60:1130,0,1513:99:116 1/1:0,28:630,63,0:63:28 0/1:0,34:626,57,0:57:34
To this
chr1 69511 69511 A G homo hetero homo hetero
Where I find and replace 0/1 with... (3 Replies)
Discussion started by: daashti
3 Replies
LEARN ABOUT OSF1
lndir
lndir(1X)lndir(1X)NAME
lndir - create a shadow directory of symbolic links to another directory tree
SYNOPSIS
lndir fromdir [todir]
DESCRIPTION
lndir makes a shadow copy todir of a directory tree fromdir, except that the shadow is not populated with real files but instead with sym-
bolic links pointing at the real files in the fromdir directory tree. This is usually useful for maintaining source code for different
machine architectures. You create a shadow directory containing links to the real source which you will have usually NFS mounted from a
machine of a different architecture, and then recompile it. The object files will be in the shadow directory, while the source files in
the shadow directory are just symlinks to the real files.
This has the advantage that if you update the source, you need not propagate the change to the other architectures by hand, since all
source in shadow directories are symlinks to the real thing: just cd to the shadow directory and recompile.
The todir argument is optional and defaults to the current directory. The fromdir argument may be relative (e.g., ../src) and is relative
to todir (not the current directory).
Note that RCS, SCCS, and CVS.adm directories are not shadowed.
Note also that if you add files, you must run lndir again. Deleting files is difficult because the symlinks will point to places that no
longer exist.
BUGS
The patch routine needs to be able to change the files. You should never run patch from a shadow directory.
Use a command like the following to clear out all files before you can relink (if the fromdir has been moved, for instance):
find todir -type l -print | xargs rm
The following command will find all files that are not directories:
find . ! -type d -print
lndir(1X)