You just rename $OUTFILE to $OUTFILE$(date +%y%m%d-%H%M%S).${DPDEVICE}, so ${OUTFILE} does no longer exist when to try to change it's access mode. You have to save the new name in a variable for later use, because 'date' might give a different timestamp when you rerun 'date'.
To display a certain line from the outfile, you can use 'grep' or 'awk' for example.
---------- Post updated at 09:06 ---------- Previous update was at 09:03 ----------
Just recongnized, that NEWFILE does not get set in the else-part just before the chmod. So you have to set NEWFILE=$OUTFILE in the else-part or - if it is OK to run 'chmod' only in the then-block - move 'chmod' just before the 'mv' command:
I'm getting the following error:
line 21: syntax error near unexpected token `done`
line 21: `done`
and I haven't been able to figure out why.
Here is my code
#!/bin/sh
if ; then
echo 'Usage: rename getexp/replStr '
exit 0
fi
arg = $1
shift
while ; do (5 Replies)
Hi,
I am running the following script through cygwin and getting below mentioned error.
*******************************************
#!/bin/sh
# constants
WORK_DIR="deploy"
INFOFILE="deploy.info"
INTROFILE="Intro.sh"
CMGMT_PKG="com.kintana.cmgmt.deploy"
DEPLOY_PREFIX="mitg"
... (2 Replies)
Hi all,
This is a script which converts hex to bin. However am finding an error while executing
syntax error near unexpected token `='
`($hexfile, $binfile) = @ARGV;'
I am running using ./fil.pl <hexfile> <binfile>
###################################################
#
# this script... (3 Replies)
What do I do here?
#!/bin/bash
payload=-1 AND 1=IF(21,BENCHMARK(5000000,MD5(CHAR(115,113,108,109,97,112))),0)#
hash=`echo -n $payload md5sum tr -d 'n' sed 'ss-sg' md5sum tr -d 'n' sed 'ss-sg'`
curl --data cs2=chronopay&cs1=$payload&cs3=$hash&transaction_type=rebill... (2 Replies)
Hi,
I am trying to read the session log through script. But it keeps showing me some error near. I have tried everything. Even tried converting the script using sed command to remove the hidden characters(\r).But nothing seems to be working.Below is the script :
#!/bin/bash
cd... (6 Replies)
I tried to execute the code but I got this error
./Array.c: line 9: syntax error near unexpected token '('
./Array.c: line 9: ' nvals = get_data(a,MAXARRAY);'
and
#include<stdio.h>
#define MAXARRAY 1000
main()
{
int a,
nvals;
nvals =... (7 Replies)
Hi all,
I have a simple script that doesn't work somehow. I can't seem to be spotting the cause of the malfunction.
count=$((1))
for item in `cat test1.txt`
printf %s `sed -n $((count))p test2.txt` > test3.txt
count=$((count+1))
do
something
done
I get ;
./why.sh: line 3:... (14 Replies)
I have 2 files like a.txt and b.txt and the content is as below
cat a.txt
810750125 117780 /BSCSQAT4A/bscsqat4a/lib/jar/wclt_common.jar
1803152428 13300 /BSCSQAT4A/bscsqat4a/lib/jar/WFMSSupportTool.jar
2663502779 67049 /BSCSQAT4A/bscsqat4a/lib/jar/wma.jar
687942896 665272... (1 Reply)
Dears,
While executing the below script im getting the error at line 30. Please let me know what changes to be done to fix this.
test.sh: line 30: syntax error near unexpected token `done'
test.sh: line 30: ` done '
#!/bin/sh
# Rev. PA1
# author: eillops
# date: 26-04-2018
#
#... (1 Reply)
detect_mouse_mvt.sh
/home/andy/bin/detect_mouse_mvt.sh: line 4: syntax error near unexpected token `('
/home/andy/bin/detect_mouse_mvt.sh: line 4: `fh = file('/dev/input/mice')'
#!/bin/bash
#
#
fh = file('/dev/input/mice')
while True:
fh.read(3)
print 'Mouse... (15 Replies)
Discussion started by: drew77
15 Replies
LEARN ABOUT CENTOS
ksshell
KSSHELL(1) General Commands Manual KSSHELL(1)NAME
ksshell -- an interactive kickstart shell
SYNOPSIS
ksflatten [-i | --input INFILE] [-o | --output OUTFILE] [-v | --version VERSION]
DESCRIPTION
ksshell is an interactive kickstart shell. It optionally takes an input kickstart file as the basis, allows the user to specify additional
kickstart commands, and then writes out the finished kickstart file to stdout or the given file name. This program supports all the usual
readline niceties including tab completion of kickstart commands and their options, though not the values those options can take.
In addition to understanding all the kickstart commands, ksshell has some builtin commands of its own to make working with kickstart files
in the context of a shell easier:
.clear Clear the existing kickstart data, including any from INFILE. This essentially starts you over from a blank state.
.quit Quit the interactive shell, either saving to the file given by OUTFILE or printing to stdout if none was given.
.show Print the current kickstart file state.
EXIT STATUS
ksflatten returns 0 on success, and 1 if VERSION is incorrect. If INFILE does not exist, a warning will be printed but the user will still
be dumped to the interactive shell.
OPTIONS -i, --input INFILE
The name of the input kickstart file.
-o, --output OUTFILE
Write the flattened kickstart file to OUTFILE, or stdout if no filename is given.
-v, --version VERSION
Use this version of kickstart syntax when processing the file, or the latest if no version is given.
SEE ALSO
ksvalidator (1), ksverdiff (1)
KSSHELL(1)