Shell Programming and Scripting

Code:

find . -maxdepth 1 -type f ! -name "*.sh" -exec mv {} /home/user/backup \;

Hi Currently it seems that only Chubler XLs code is working the way I want

Code:

bash-3.00$ ls  -ltr
total 8
-rw-r--r--   1 vprabhu  deloitte       0 Apr  4 03:14 startServer.sh
-rw-r--r--   1 vprabhu  deloitte       0 Apr  4 03:14 jra_managed1_20110316.jfr
-rw-r--r--   1 vprabhu  deloitte       0 Apr  4 03:14 config.xml.20110316_1
drwxr-xr-x   2 vprabhu  deloitte       3 Apr  4 03:15 security.20110316.stress
-rwxr-xr-x   1 vprabhu  deloitte     213 Apr  4 03:17 ChublerXL.sh

Runnign Chublers code below

Code:

bash-3.00$ ./ChublerXL.sh 
mv config.xml.20110316_1 ./backup
mv jra_managed1_20110316.jfr ./backup

Vistastar your ls statement only prints out the sh scripts with *, I havent tried with mv yet, but would this behavior change if I used the mv?

Code:

bash-3.00$ ls -F | grep -v '.sh$\|/'
ChublerXL.sh*
config.xml.20110316_1
jra_managed1_20110316.jfr
security.20110316.stress/
startServer.sh

I dont think I have ruby on my serverrs

Code:

bash-3.00$ man ruby
No manual entry for ruby.

I cant use the maxdepth option for some reason

Code:

bash-3.00$ find . -maxdepth 1 -type f -name "*[!.sh]"
find: bad option -maxdepth
find: [-H | -L] path-list predicate-list

Any Ideas?

Thanks

Code:

find ./* -prune -type f ! -name \*.sh -exec mv {} /home/user/backup \;

Note the wildcard in the ./* PATH description ... , if you omit it, the -prune option will not behave as you expect.


(make a test without the -exec mv ... command at first so you can ensure that the selection fits with your requirements.

Well, Chubler_XL's solution could be written on one line if one was so inclined (there's nothing in the shell grammar that prevents it).

Also, the approaches are not equivalent. Chubler_XL's solution can handle any valid filename (if $file after mv is quoted), regardless of how ludicrous it may be. Your approach, however, could be wrecked by field splitting and pathname expansion after the command substitution, if any of the filenames contain IFS characters (spaces would be the most likely culprit) or glob metacharacters (and asterisks, question marks, brackets).

The -F option to ls will add an asterisk after any shell scripts with an executable bit set (which is to be expected but not a certainty for a .sh file). The grep should probably handle an optional * after .sh.

Lastly, your grep regular expression is underspecified. The ".sh" will not just match names ending in ".sh" but also "ash", "ish", etc. The dot is a metacharacter and needs to be quoted to match itself.

Regards,
Alister

---------- Post updated at 11:17 AM ---------- Previous update was at 11:12 AM ----------

That's incorrect. Bracketed expressions in globs do not work that way. That actually matches any file whose final character is not a "." or and "s" or an "h", and not a file whose name does not end in the string ".sh".

Regards,
Alister

This approach also has issues when no *.sh files exist, or when too many exist and the command line limit is exceeded.

But the correct way is?...

Well, taking correction from rdcwayx's post

! -name "*.sh"

Thanks for the observation.

Regards.