Sponsored Content
Full Discussion: shopt -s nullglob
Top Forums Shell Programming and Scripting shopt -s nullglob Post 302254561 by msb65 on Tuesday 4th of November 2008 05:53:14 PM
Old 11-04-2008
shopt -s nullglob

Hi,

I am using BASH. In a directory there are files that match either of the following 2 patterns: [AST]*.L1A_[GL]AC* or S*.L1A_MLAC*

I would like to write a script that will include a for loop, where for each file in the directory, a certain function will be performed. For example:

for FILE in [AST]*.L1A_[GL]AC* S*.L1A_MLAC*; do
echo $FILE
done

The content of the directory will be random, and there are 3 potential scenarios: 1) Files of both patterns exist in the directory, 2) Only files of the 1st pattern exist, 3) Only files of the 2nd pattern exist. The last two scenarios are problematic as one of the patterns won't be matched, resulting in my script behaving oddly.

- I believe the way around this is to use the shopt -s nullglob option. Does anyone have any other ideas?

- MAIN QUESTION: Where in the code should I put the shopt -s nullglob and shopt -u nullglob? Of course the shopt -s nullglob should be set immediately before the the beginning of the for loop. But, can the shopt -u nullglob be immediately after the beginning of the for loop (ie):

shopt -s nullglob
for FILE in [AST]*.L1A_[GL]AC* S*.L1A_MLAC*; do
shopt -u nullglob
echo $FILE
done

OR after the conclusion of the for loop (ie):

shopt -s nullglob
for FILE in [AST]*.L1A_[GL]AC* S*.L1A_MLAC*; do
echo $FILE
done
shopt -u nullglob

The reason I ask is because I will of course have more complicated code within the for loop, and only want the shopt nullglob command to affect the pattern matching when calling the for loop.

Thanks for your help.

Mike
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bash 'shopt' doubt

Hi, I am using bash shell's extended pattern matching. What tweak the following code needs in order to get the expected output? shopt -s extglob f="a@b@_c@d@_e" echo "${f/@(@|@_)/__}" My expected output is: a__b__c__d__e but the actual output is: a__b@_c@d@_e # that is, how to... (3 Replies)
Discussion started by: royalibrahim
3 Replies

2. Shell Programming and Scripting

Bash, Bourne, and nullglob

I have a script that start out with this: #!/sbin/sh Several things run. However I cannot get: shopt -s nullglob to run in Bourne. I get: shopt: not found So within the main script (after #!/sbin/sh at the top) I start bash with: bash and try to run what I need with: shopt -s... (2 Replies)
Discussion started by: crowman
2 Replies

3. UNIX for Advanced & Expert Users

Shopt -s histappend

What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file. # When the shell exits, append to the history file instead of overwriting it shopt -s histappend (3 Replies)
Discussion started by: cokedude
3 Replies
thread_halt_self(9r)													      thread_halt_self(9r)

NAME
thread_halt_self - General: Handles asynchronous traps for self-terminating kernel threads SYNOPSIS
void thread_halt_self( void ); ARGUMENTS
None DESCRIPTION
The thread_halt_self routine performs the work associated with a variety of asynchronous traps (ASTs) for a kernel thread that terminates itself. A kernel thread terminates itself (or one kernel thread terminates another kernel thread) by calling the thread_terminate routine. The thread_halt_self routine examines the AST-related member of the thread structure pointer associated with the kernel thread that wants to terminate itself. This thread structure pointer was returned in a previous call to kernel_isrthread or kernel_thread_w_arg and passed by you to the thread_terminate routine. This AST-related member is set to a bit that identifies the specific AST trap associated with this kernel thread. Based on the AST bit set in this member, thread_halt_self does the appropriate cleanup work before the kernel thread exits from the kernel. NOTES
A kernel thread that terminates itself must call thread_halt_self immediately after the call to thread_terminate. The reason for this is that thread_terminate only prepares the self-terminating kernel thread to stop execution. The thread_halt_self routine completes the work needed to stop execution of the self-terminating kernel thread by performing the appropriate cleanup work. RETURN VALUES
None SEE ALSO
Routines: thread_terminate(9r) thread_halt_self(9r)
All times are GMT -4. The time now is 03:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy