Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: ksh on HP-UX -- variable expansion
Top Forums UNIX for Dummies Questions & Answers ksh on HP-UX -- variable expansion Post 61628 by dangral on Sunday 6th of February 2005 10:34:26 PM
Old 02-06-2005
ksh on HP-UX -- variable expansion
We have a script that runs in ksh on HP-UX 11.11. It takes three arguments. The last argument can be a filename or wildcard character. For example:

Code:
script -s hello -t goodbye '*.d*'

In a case such as this, I would wrap single quotes around the final argument because I dont want the shell to attempt to expand it. I want the string *.d* to get passed to the script.

The problem:

If there is a filename that matches the pattern of the final argument, that filename(s) get passed onto the script, instead of *.d*
How do I make sure the string I put in the command line gets passed on, no matter what is in the current directory?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Basic variable expansion not working...

#!/usr/bin/bash if then echo "Not valid arguments entered. Just username should be entered." else USER_NAME=$1 FILE_NAME=$USER_NAME.info UNN=STUDIN\\\\$1 echo $UNN last STUDIN\\\\$1 last UNN If I type `last STUDIN\\eip060` it works but if I try to expand it with variable it is... (5 Replies)
Discussion started by: Zammy_bg
5 Replies

2. Shell Programming and Scripting

bash - delay expansion of variable

Hello - I have a bash script which does some logging, and I'd like to include the line number of the echo statement that pipes into $LOGGER: MYPID=$$ MYNAME=`basename $0` LOGGER="/usr/bin/logger -t $MYNAME($LINENO) -p daemon.error" ... echo 'this is an entry into the log file' | $LOGGER ... (3 Replies)
Discussion started by: scandora
3 Replies

3. UNIX for Dummies Questions & Answers

Variable brace expansion

I'm in the habit of using the following type of loop structure: for num in `seq $1 $2` do command doneWhile `seq $1 $2` is not exactly a huge resource hog, I would like to learn a better way. It seems that brace expansion is a good way to go: for num in {3..10}The problem, though, is... (2 Replies)
Discussion started by: treesloth
2 Replies

4. Shell Programming and Scripting

Bash variable delayed expansion?

i write a batch file , here is the content. dirname='date +%Y-%m-%d' mkdir dirname but it doen's work, it just create a folder named date and +%Y-%m-%d. i have tried run the command seperately in the bash prompt. after the first sentence executed , i use $dirname to watch the value of... (4 Replies)
Discussion started by: premotheus
4 Replies

5. Shell Programming and Scripting

Variable expansion in sed

The objective of the code below is to create sed script to be later executed. However, it bonks because $ARCHIVENAME expands to a directory specification so the forward slashes cause problems. I can think of a few solutions that would involve redesigning the process, but I'm hoping there might be... (4 Replies)
Discussion started by: tiggyboo
4 Replies

6. Shell Programming and Scripting

delay variable expansion

Hi forum, in my bash script I've many lines executing commands with redirection to log files. ... xyz_cmd 2>&1 > $BASENAME.$LINENO The trailing part of these lines doesn't look nice and I like to put it into a variable. The (not working) idea is something like that ... (3 Replies)
Discussion started by: wolfi089
3 Replies

7. UNIX for Dummies Questions & Answers

Can I use a variable with brace expansion?

So, I was bored on the train today, and was thinking of ways to loop through elements of an array. I came up with the following simple script, but it doesn't work as brace expansion doesn't seem to work with variables. Is there something I'm missing, or does the shell just not work like this? ... (4 Replies)
Discussion started by: DeCoTwc
4 Replies

8. Shell Programming and Scripting

Protecting variable indicator ($) from expansion

Hello, I use a lot this command to edit a bunch of files at once find . -name filename" | xargs -ifoo sh -c 'echo foo ; sed "s/pattern1/pattern2/" foo > ./tmp ; mv -f ./tmp foo' I'm trying to put a function on my .bashrc file. function loopSed() { local filename=$1 local... (2 Replies)
Discussion started by: phollox
2 Replies

9. Shell Programming and Scripting

Shell variable expansion in awk

I want to split one file input.tab into two separate ones, odd lines to input_reads1.txt, even lines to input_reads2.txt for a serial of files with similar name pattern. Also I want to "match" input/output file names to keep consistency of file name: CSEL_02.0_input.tab CSEL_03.4_input.tab... (2 Replies)
Discussion started by: yifangt
2 Replies

10. Shell Programming and Scripting

Bash variable expansion

Hello. The file /etc/fstab contains UUID=957c3295-9944-1593-82e2-2b90dede4312 / ext4 noatime,discard,acl,user_xattr 1 1 I fill a variable SOME_LINE=$( cat /etc/fstab | grep \/\..*ext4 | grep noatime,discard )echo $SOME_LINE... (3 Replies)
Discussion started by: jcdole
3 Replies

LEARN ABOUT DEBIAN

dh_installinit

DH_INSTALLINIT(1)						     Debhelper							 DH_INSTALLINIT(1)

NAME

       dh_installinit - install init scripts and/or upstart jobs into package build directories

SYNOPSIS

       dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params]

DESCRIPTION

       dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files, as well as upstart
       job files into package build directories.

       It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop
       the init scripts.

FILES

       debian/package.init
	   If this exists, it is installed into etc/init.d/package in the package build directory.

       debian/package.default
	   If this exists, it is installed into etc/default/package in the package build directory.

       debian/package.upstart
	   If this exists, it is installed into etc/init/package.conf in the package build directory.

OPTIONS

       -n, --noscripts
	   Do not modify postinst/postrm/prerm scripts.

       -o, --onlyscripts
	   Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the
	   init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.

       -R, --restart-after-upgrade
	   Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which
	   stops the script in the prerm, and starts it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       -r, --no-restart-on-upgrade
	   Do not stop init script on upgrade.

       --no-start
	   Do not start the init script on install or upgrade, or stop it on removal.  Only call update-rc.d. Useful for rcS scripts.

       -d, --remove-d
	   Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ ,
	   and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be
	   useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.)

       -uparams --update-rcd-params=params
       -- params
	   Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8).

       --name=name
	   Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which
	   is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init,
	   debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and
	   debian/package.upstart.

       --init-script=scriptname
	   Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file,
	   if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks
	   like package.scriptname and if so will install it as the init script in preference to the files it normally installs.

	   This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs.

       --error-handler=function
	   Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts,
	   before the #DEBHELPER# token.

NOTES

       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
       instances of the same text to be added to maintainer scripts.

SEE ALSO

       debhelper(7)

       This program is a part of debhelper.

AUTHORS

       Joey Hess <joeyh@debian.org>

       Steve Langasek <steve.langasek@canonical.com>

9.20120909							    2012-04-10							 DH_INSTALLINIT(1)
All times are GMT -4. The time now is 03:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy