I think cabrao meant that you didn't need the *. Besides, with your grep in single quotes the shell would not expand it in any way so it would look for filenames literally including v00*
At the very least in a regular expression you would need .* (without single quotes)
A * in a regular expression matches 0 or more of the last expression (in your case the character 0), whereas . means match any character and .* matches 0 or more of any character.
You should also change your ls to "ls -1".
I don't know the names of the files in your $program directory, but:
should also do the same thing.
Don't confuse the * in how the shell expands filenames with * in a regular expression - they're not the same thing.
Anybody know what's wrong with this syntax?
awk -v job="$job" 'BEGIN { FS="|"}
{print $1,$2," ",$4," ",$3\n,$5,"\n"}' list
It's keeping give me this message:
awk: syntax error near line 1
awk: bailing out near line 1
It seems awk has problem with my BEGIN command.
Any... (8 Replies)
Does anybody know how to print a variable passed to awk command?
awk -F"|" 'BEGIN {print $job,"\n","Question \n"} {print $1,$2$4," ",$3}' "job=$job1" file1
I am trying to pass job the variable job1.
the output is blank.
?? (3 Replies)
Hi,
I have a unix script which can accept n number of parameters .
I can get the parameter count using the following command and assign it to a variable
file_count=$#
Is there a similar command through which i can assign a variable all the values that i have passed as a parameter
... (2 Replies)
Hi,
I am facing a challenge in fixing an issue in my installation scripts.Here is a situation:
There are 3 files which are invoked at a below given order:
Installer.ksh----->Installer.xml(Ant script)------->common.ksh
I am outputting a message from common.ksh at a terminal, after that trying to... (3 Replies)
Hi everybody,
Currently, I have a script which access a remote computer via SSH, go to a folder already defined in the code and then executes a program in it, just like that:
ssh user@host << EOI
cd path
./file
EOI
It executes fine, but now I want to pass an argument in the command... (2 Replies)
I am having difficulties with the fllowing script:
!/bin/sh
voicemaildir=/var/spool/asterisk/voicemail/$1/$2/INBOX/
echo `date` ':' $voicemaildir >> /var/log/voicemail-notify.log
for audiofile in `ls $voicemaildir/*.wav`; do
transcriptfile=${audiofile/wav/transcript}
... (4 Replies)
I have a script.
#!/bin/sh
cur_$1_modify_time=Hello
echo "cur_$1_modify_time"
When I run like
sh /root/script1 jj
I expect value "Hello" being assigned to variable "cur_jj_modify_time" and output being "Hello" ie echoing $cur_jj_modify_time
But the output comes as
# sh... (3 Replies)
Hello,
I am writing a script which is not giving the desired result. When I check the content of the 'InputFile_009_0.sh', it shows following with missing Index in this command
sed -i "s/L1ITMBLT.root/L1ITMBLT_"".root/g" run_DttfFromCombinedPrimitives_cfg.py
of .
Any help?
... (13 Replies)
In the bash below the variable date displays in the echo. However when I use it in the for loop it does not. Basically, the user inputs a date then that date is converted to the desired format of (month-day-year, no leading 0). That input is used in the for loop to return every file that matches... (5 Replies)
Discussion started by: cmccabe
5 Replies
LEARN ABOUT NETBSD
devscripts.conf
DEVSCRIPTS.CONF(5) File Formats Manual DEVSCRIPTS.CONF(5)NAME
devscripts.conf - configuration file for the devscripts package
DESCRIPTION
The devscripts package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack-
ages. Many of these have options which can be configured on a system-wide and per-user basis.
Every script in the devscripts package which makes use of values from these configuration files describes the specific settings recognised
in its own manpage. (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts
| grep /usr/bin.)
The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings. They are written
with bash(1) syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of
the devscripts scripts. Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded
as equivalent to the default setting.
All variable names are written in uppercase, and begin with the script name. Package-wide variables begin with "DEVSCRIPTS", and are
listed below, as well as in the relevant manpages.
For a list of all of the available options variables, along with their default settings, see the example configuration file
/usr/share/doc/devscripts/devscripts.conf.ex. This is copied to /etc/devscripts.conf when the devscripts package is first installed.
Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack-
age is upgraded.
Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option.
PACKAGE-WIDE VARIABLES
The currently recognised package-wide variables are:
DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
These variables control scripts which change directory to find a debian/changelog file or suchlike, and some other miscellaneous
cases. In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions will be performed.
The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but
this list may change with time (and I may not remember to update this manpage). Please see the manpages of individual scripts for
details of the specific behaviour for each script.
SEE ALSO devscripts(1) and /usr/share/doc/devscripts/README.gz.
AUTHOR
This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>.
DEBIAN Debian Utilities DEVSCRIPTS.CONF(5)