Sponsored Content
Full Discussion: How to use wildcard * in if?
Top Forums Shell Programming and Scripting How to use wildcard * in if? Post 302520193 by 116@434 on Friday 6th of May 2011 05:35:01 AM
Old 05-06-2011
Code:
 
while read line; do
 
if echo $line|grep '^[^|]*|[^|]*|[^|]*|Apple|'; then
 
fi
 
done <filename

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Find wildcard .shtml files in wildcard directories and removing them- How's it done?

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)
Discussion started by: Neko
1 Replies

2. UNIX for Dummies Questions & Answers

wildcard

what will the cmd below do? ls *.3 1 members mentions that to seek all permutations and combinations of the mp3 extension ill have to use curly braces, {} and not, . what then will do? (13 Replies)
Discussion started by: abhi
13 Replies

3. Shell Programming and Scripting

Wildcard comparison

Just a quick question: if I want to do a comparison with a wildcard in a shell script, do i just use '*'? Heres what I have: elif ; then continue but that doesnt evaluate right. It tries to compare against the literal '/apps*' instead of anything that begins with '/apps' (2 Replies)
Discussion started by: rdudejr
2 Replies

4. Shell Programming and Scripting

wildcard

Hi, I have this code to search all "cif" files using wildcard for file in *.cif do grep "Uiso" $file | awk '{ print $3, $4, $5 }' > tet done I get this error "grep: *.cif: No such file or directory" Please where am I going wrong!!! Thank you in advance (6 Replies)
Discussion started by: princessotes
6 Replies

5. UNIX for Advanced & Expert Users

wildcard help

Can someone please explain the wildcards in this. How is this recursive? When I put this in my terminal it recursively displayed everything. ls .* * (6 Replies)
Discussion started by: cokedude
6 Replies

6. Shell Programming and Scripting

wildcard help!!

i have got heaps of files (.pdf, .txt and .doc) files in one folder, i am making a program in PERL that helps me find the files i want easier using shell wildcard, something like this!! print "Enter a pattern: (must be in )"; $input = <STDIN>; if (The input is in and valid wildcard... (3 Replies)
Discussion started by: bshell_1214
3 Replies

7. Shell Programming and Scripting

Using wildcard in if statement

I'm trying to make a small script to see if you say a specific word, in bash. Here is my code so far : if ]; then echo "You typed Something Device Something" fi exit 0 It does not echo what it should, even if i type something along the lines of "random Device stuff" Please help,... (2 Replies)
Discussion started by: DuskFall
2 Replies

8. Shell Programming and Scripting

Wildcard in ls

Hi Experts, I want to use ls in the below form: ls -l *.{txt,TXT} (working fine) but when i am declaring a variable, VAR="*.{txt,TXT}" ls -l $VAR is not working. Please help. Thanks. (4 Replies)
Discussion started by: sugarcane
4 Replies

9. Shell Programming and Scripting

Wildcard for grep

GNU grep with Oracle Linux 6.3 I want to grep for strings starting with the pattern ora and and having the words r2j in it. It should return the lines highlighted in red below. But , I think I am not using wildcard for multiple characters correctly. $ cat someText.txt ora_pmon_jcpprdvp1... (3 Replies)
Discussion started by: kraljic
3 Replies

10. OS X (Apple)

Help with wildcard

CD_numb is AM017 this code: set the_Firstcom_CD to (do shell script "ls -d '/volumes/audioNAS/Firstcom/Access Music/' ") & CD_numb gives me this: "/volumes/audioNAS/Firstcom/Access Music/AM017" the item I am looking for is AM017Q. I can get the "*" syntax right so it never finder... (7 Replies)
Discussion started by: sbrady
7 Replies
SubmitDiagInfo(8)					    BSD System Manager's Manual 					 SubmitDiagInfo(8)

NAME
SubmitDiagInfo -- sends diagnostic information to Apple SYNOPSIS
SubmitDiagInfo DESCRIPTION
SubmitDiagInfo is a system process which runs periodically. If the user has opted-in for automatic reporting of diagnostic and usage infor- mation, then SubmitDiagInfo collects and sends to Apple any recent diagnostic information which has not yet been sent to Apple. SubmitDiagInfo also cleans up any diagnostic and usage information which was created more than one month ago and is no longer needed. Sending diagnostic and usage reports to Apple helps us improve the quality and performance of our products and services. It helps Apple identify common usage trends and issues that enable us to allocate our resources efficiently, and it helps us provide better support services to you and other customers. All of the diagnostic and usage information is collected anonymously from your computer in a way that does not personally identify you. Reports may include the following information: - Details about application or system crashes, freezes, or kernel panics. - Information about events on your computer (e.g. whether a certain function, such as waking your computer was successful or not). - Usage information (e.g. data about how Apple and third party software, hardware and services are being used). Automatic reporting of diagnostic information is off by default and no information is sent to Apple unless a user has opted-in to automatic collection of diagnostic information. A user is offered the opportunity to opt-in for automatic collection of additional diagnostic and usage information after the user has manually sent a crash, hang or panic report to Apple. Users may at any time opt in or out of automatic reporting in the Security & Privacy pane of the System Preferences application under the "Privacy" tab. All diagnostic and usage information which is eligible for automatic reporting is visible in the Console application under the "DIAGNOSTIC AND USAGE INFORMATION" heading in the application's sidebar. (The information appears here even if a user has not yet opted-in for automatic reporting.) For security purposes, some system diagnostic information will only be visible to admin users and will only be submitted when an admin user is logged in. Users who need technical support should use http://www.apple.com/support or other authorized support channels. Developers who are ADC mem- bers should submit bug reports using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug reporter. SEE ALSO
ReportCrash(8) Mac OS June 2, 2019 Mac OS
All times are GMT -4. The time now is 10:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy