The UNIX and Linux Forums  

Go Back   The UNIX and Linux Forums > Top Forums > Shell Programming and Scripting
.
google unix.com



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
bash vs. sh msb65 Shell Programming and Scripting 10 09-18-2008 03:25 PM
bash and ksh: variable lost in loop in bash? estienne Shell Programming and Scripting 2 08-25-2008 03:09 PM
passing variable from bash to perl from bash script arsidh Shell Programming and Scripting 10 06-04-2008 01:25 PM
Why generate "ash and bash" different output for same bash script? s. murat Shell Programming and Scripting 0 05-26-2008 08:19 AM
Bash under AIX 5.3 taupin AIX 4 03-21-2008 06:03 AM

Closed Thread
English Japanese Spanish French German Portuguese Italian Dutch Swedish Russian Norwegian Hungarian Hebrew Danish Bulgarian Greek Powered by Powered by Google
 
LinkBack Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old 10-12-2008
mindOnMy$ mindOnMy$ is offline
Registered User
  
 

Join Date: Oct 2008
Posts: 2
Question What does this do in bash: ${pid:-}

As i understand it, this means
if pid is
a) unset, or
b) set to null
then replace with the value on the right of the minus sign--which is null

This confuses me because
a) I thought if a variable isn't set to anything it's automatically null. If not then what is an uninitiated variable set to?
b) if the variable is already set to null, then why replace it with another null?

I see this on line 74 in the file /lib/lsb/init-functions (I'm using hardy heron ubuntu)
Here's an excerpt from the file:
Code:
if [ -z "${pidfile:-}" ]; then 
    pidfile=/var/run/${1##*/}.pid 
fi
  #2 (permalink)  
Old 10-12-2008
jim mcnamara jim mcnamara is online now Forum Staff  
...@...
  
 

Join Date: Feb 2004
Location: NM
Posts: 5,771
The code is making sure that if the pid variable is unset it becomes null (or zero-length).
unset and null are different. null means that variable exists in memory and is "", unset means bash never heard of it before.

In coding, whenver you create a new variable you want to set it to a known state. In C you set a string to be zero-length, an integer to zero. This is the same idea.
  #3 (permalink)  
Old 10-12-2008
otheus's Avatar
otheus otheus is offline Forum Staff  
Moderator ala Mode
  
 

Join Date: Feb 2007
Location: Innsbruck, Austria
Posts: 1,886
Granted, null and zero-length are different, but the shell expands them the same way. So really there's no reason for the code as is. It could simply be:
Code:
if [ -z "$pidfile" ] ;then 
  # blah blah
fi
There's actually a simpler way.
Code:
pidfile=${pidfile:-/var/run/${1##*/}.pid}
  #4 (permalink)  
Old 10-13-2008
mindOnMy$ mindOnMy$ is offline
Registered User
  
 

Join Date: Oct 2008
Posts: 2
ahh, I see. now it all makes sense. thnx!
Closed Thread

Bookmarks

Tags
variable expansion programming bash

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT -4. The time now is 06:03 AM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited. Language Translations Powered by .
vBCredits v1.4 Copyright ©2007 - 2008, PixelFX Studios
The UNIX and Linux Forums Content Copyright ©1993-2009. All Rights Reserved.Ad Management by RedTyger

Content Relevant URLs by vBSEO 3.2.0