|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem with search pattern | gantagoru | Shell Programming and Scripting | 1 | 05-27-2008 10:43 AM |
| Problem with regexp for IP-Adress Pattern | desertchannel | Shell Programming and Scripting | 9 | 05-26-2008 03:37 AM |
| pattern matching problem | namishtiwari | Shell Programming and Scripting | 2 | 05-23-2008 08:33 AM |
| problem with CASE pattern matching | gummysweets | Shell Programming and Scripting | 2 | 03-18-2008 11:30 AM |
| pattern matching problem | rein | Shell Programming and Scripting | 8 | 10-27-2007 12:44 AM |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
04-23-2007
|
||||
|
||||
|
Pattern expansion problem
All,
I have a shell script which executes the below command find $1 -name $2 -print > ${Backup}/FileFind.txt I have $2 sometimes coming with the below values. .[a-z]* When I go to the log after the execution of the script, .[a-z]* gets expanded to .developer.adm instead of searching for all the . files like .profile, .odbc etc. How do I comeover this issue? Your help will be greatly appreciated. Thanks. |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Threaded Mode
