Can someone explain to me how this above script works, I got it from a friend but not able to understand what is happening inside.
when is do this ./script.sh file.txt This script is changing the DS: * value in the file sequencially from 1to8. But I to like to understand how this script is working.
Thank you in advance!!!
Moderator's Comments:
Please use CODE tags when displaying sample input, output, and code segments.
Last edited by Don Cragun; 03-28-2018 at 08:14 AM..
Reason: Add CODE and ICODE tags.
hi ,
i am writing a script to copy the MQ messages from onw queue to another. The following i got from one site, but i di not understand , can anyone explain.
/root/scripts/sap/q -m$Q_MANAGER -i$Q_NAME_SRC_1 -F/logs/mq/MQ_COPYdump_$Q_NAME_SRC_1.$$
/root/scripts/sap/q -m$Q_MANAGER... (0 Replies)
I am relatively new to Shell Scripting. I can't understand the following two scripts. Can someone please spare a minute to explain?
1) content s of file a are
(021) 654-1234
sed 's/(//g;s/)//g;s/ /-/g' a
021-654-1234
2)cut -d: -f1,3,7 /etc/passwd |sort -t: +1n gives error (3 Replies)
Hi All;
Is there anybody can explain this script please?
trap 'C_logmsg "F" "CNTL/c OS signal trapped, Script ${G_SCRIPTNAME] terminated"; exit 1' 2
trap 'C_logmsg "F" "Kill Job Event sent from the Console, Script ${G_SCRIPTNAME] terminated"; exit 1' 15 (3 Replies)
Can u please explain what it is doing
#!/bin/sh
fullyear=`/home/local/bin/datemmdd 1`"."`date +%Y`
uehist=/u05/home/celldba/utility/ue/prod/history
echo $fullyear
cd $uehist
ls -ltr pwroutages.master.$fullyear* | awk '{print $9}' > /u01/home/celldba/tmp/pwroutages_master_all_tmp
while... (2 Replies)
Hi All,
I have a ksh script & would like to understand mening of below lines in script,
Starting lines of script is as below,
#!/bin/ksh
#%W% %I% %D% %T% ---- ???
#%W%G --- ???
num_ctrl_files=0
OS=`uname`
if
then
//g' | egrep -v '(.sh:|.ksh:)' | sed 's/^.*://g' | sed 's/^M//g' |... (6 Replies)
Hi
i have one script and i am running it but not getting current output so i want to understand how to input in the script.
when i do help then i am getting below massage
thanks
got it (1 Reply)
Hello world! Can someone please explain me how this code works? I'ts supposed to find words in a dictionary and show the anagrams of the words.
{
part = word2key($1)
data = $1
}
function word2key(word, a, i, x, result)
{
x = split(word, a, "")
asort(a)
... (1 Reply)
New to korn shel1 and having an issue. The following is suppose to read the parameter values from files in a source directory and then pass them on to a log file in a different directory, The ArchiveTracker scripts is suppose to call the parameterreader script to exact the parameter values and... (3 Replies)
Please help me to understand the below 3 lines of code.execute shell in jenkins
1)APP_IP=$( docker inspect --format '{{ .NetworkSettings.Networks.'"$DOCKER_NETWORK_NAME"'.IPAddress }}' ${PROJECT_NAME_KEY}"-CI" )
2)HOST_WORKSPACE=$(echo ${WORKSPACE} | sed... (1 Reply)
Discussion started by: naresh85
1 Replies
LEARN ABOUT DEBIAN
apsfilter-bug
APSFILTER-BUG(1) BSD General Commands Manual APSFILTER-BUG(1)NAME
apsfilter-bug -- create a half-automatic bug report for apsfilter
SYNOPSIS
apsfilter-bug
OPTIONS
none
DESCRIPTION
With the apsfilter-bug script you can automatically create a bug report for apsfilter(1). A template report file is created which you can
edit with your favourite editor ( emacs(1) by default, or whatever is entered in the environment variable EDITOR ).
You will see a couple of lines starting with '#'; these lines will be removed before the report is sent. So if you want to use the '#' char-
acter at the beginning of a line, just indent it with a space.
A very important piece of the bug report is the debugging log created by aps2file(1), probably with a command like
aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
Unless you don't even have a chance to create a debugging log, it is crucial for serious bug hunting.
After you have filled in as much (useful) information as possible, you must save the file under its original name, then exit your editor.
If you invoked apsfilter-bug by accident, or if you need some additional system information to include into the bug report, just exit your
editor without saving the file.
NOTES
In addition to the stuff you've edited, some more information is appended to the bug report automatically:
apsfilter version 7.2.6-stable
ghostscript version (from 'gs --version')
system id (from 'uname -a')
configure options --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-awk=/usr/bin/awk --with-sendmail=/usr/sbin/sendmail
shell executable /bin/bash
awk executable /usr/bin/awk
sendmail executable /usr/sbin/sendmail
FILES
/usr/bin/aps2file script to create debugging output
SEE ALSO apsfilter(1), aps2file(1)BUGS
See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.
Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which
asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via e-mail to the proper
apsfilter mailinglist.
If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save
the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug
and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the
mail to the apsfilter mailinglist.
Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works.
Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing /bin/sh or
bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).
DOCUMENTATION
See official apsfilter homepage
http://www.apsfilter.org/handbook.html Apsfilter Handbook including the Frequently Asked Questions (FAQ)
USER FORUM
Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.org. The above section BUGS and the file
HOWTO-BUGREPORTS tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage
aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.
HISTORY
The apsfilter-bug manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.
BSD Dec 26, 2001 BSD