Off the top of my head (so there might be better solutions)...
Assuming that the current working directory is the root of the portion of the file tree that you wish to parse, here are two possibilities. The first, I believe, is more efficient, but isn't bash friendly (ksh only). The second should run in either bash or ksh. Run to see what it would create/move and then remove the 'echo' to actually do the work.
Code:
#!/usr/bin/env ksh
# ksh only!
typeset -A dhash
find . -name "*.dpx"| while read f
do
path=${f%/*}
if [[ -z ${dhash[$path/]} ]]
then
echo "mkdir $path/2880x1640"
dhash[$path/]=1;
fi
echo mv $f $path/2880x1640/
done
Code:
# not efficient as it has to stat the target directory for every file, but works in bash.
find . -name "*.dpx"| while read f
do
path=${f%/*}
if [[ ! -d $path/2880x1640 ]]
then
echo "mkdir $path/2880x1640"
fi
echo mv $f $path/2880x1640/
done
hello
I have a file system with 737 Go of data (oracle)
I want to add 230 Go.
IBM technician says to me that it's better (for performance) to backup the file system, rebuild it with the new 250Go and restore it....
737 Go to backup, it is not very simple... !!!!
You confirm what says the... (6 Replies)
I'm developing a generic script to catenate all files found in a given directory.
The problem I've got is that the depth of the given directory is unknown, so I end up with some catenated directories. My unix isn't that hot and I'm at a loss.
Heres an extract from the script
cd $1
for i in... (4 Replies)
Hi,
I am quite sure that I am posting a question in the very wrong forum but I have to give a try. It's a question about UNIX theory. I don't have any clue of how to solve this question. If someone could kindly provide some good references or give me the formulas, it will be really... (1 Reply)
The /src file is obviously designed to contain source code, so when I download programs, I should put them in /src (because they contain the source files + the executables)? What do most people do with the executables? Do they copy them to /bin, make links to them in /bin, or just leave them in... (4 Replies)
I manage a spam filter for the organization I work for. I've been trying to get the others here to stop white listing by domain name since that can be easily spoofed. One of the obstacles, however, is that there doesn't seem to be an easy way to determine the legitimate outgoing SMTP server IP... (0 Replies)
Hi All,
Through mailx command, we are able to send mail to all users within the organization but not outside the organization.
I need to work with Admin to configure it. Can someone tell me on what are the things needs be done to enable it.
i have checked the resolv.conf, it shows only... (1 Reply)
Hi All,
The script below read the path and searches for the directories/subdirectories and for the files. If files are found in the sub directories then read the content of the all files and put the content in csv(comma delimted) format and the call the write to xml function to write the
std... (1 Reply)
Hi,
I have got a file with 6K records and I want to delete 500 records from this file which match the values present in another file.
Format of the both the files is different.
Example : File 1 record
CCCCCC 11292562ABCDEF MBR/PSF6/108100502/BEN01XXX XXX
Example : File 2 record... (1 Reply)
Discussion started by: Nikhath
1 Replies
LEARN ABOUT SUSE
git-clean
GIT-CLEAN(1) Git Manual GIT-CLEAN(1)NAME
git-clean - Remove untracked files from the working tree
SYNOPSIS
git clean [-d] [-f] [-n] [-q] [-x | -X] [--] <path>...
DESCRIPTION
Cleans the working tree by recursively removing files that are not under version control, starting from the current directory.
Normally, only files unknown to git are removed, but if the -x option is specified, ignored files are also removed. This can, for example,
be useful to remove all build products.
If any optional <path>... arguments are given, only those paths are affected.
OPTIONS -d
Remove untracked directories in addition to untracked files. If an untracked directory is managed by a different git repository, it is
not removed by default. Use -f option twice if you really want to remove such a directory.
-f, --force
If the git configuration variable clean.requireForce is not set to false, git clean will refuse to run unless given -f or -n.
-n, --dry-run
Don't actually remove anything, just show what would be done.
-q, --quiet
Be quiet, only report errors, but not the files that are successfully removed.
-x
Don't use the ignore rules. This allows removing all untracked files, including build products. This can be used (possibly in
conjunction with git reset) to create a pristine working directory to test a clean build.
-X
Remove only files ignored by git. This may be useful to rebuild everything from scratch, but keep manually created files.
AUTHOR
Written by Pavel Roskin <proski@gnu.org[1]>
GIT
Part of the git(1) suite
NOTES
1. proski@gnu.org
mailto:proski@gnu.org
Git 1.7.1 07/05/2010 GIT-CLEAN(1)