Sed script error

chinna448 · 07-03-2019, 12:03 AM

I am trying to implement a sed script to a notepad file.

And I am getting below error,

sed: can't find label for jump to 'ak'

not sure what is wrong

scasey · 07-03-2019, 12:05 AM

Pretty hard for us to help without seeing the sed command that’s causing the error...

notepad? On Linux???

chinna448 · 07-03-2019, 12:16 AM

linux

chinna448 · 07-03-2019, 12:20 AM

My script is something like below to replace port in the file template.txt and rename as test.txt. This script is named as test .sh

#!/bin/bash   

filename="test.txt
port="80"

cp template.txt $filename 
sed -i.bak "s/port/$port/g" $filename 

I am implementing script as below and getting error as below,

#test.sh
sed: can't find label for jump to 'ak'
sed: can't find label for jump to 'ak'
sed: can't find label for jump to 'ak'
sed: can't find label for jump to 'ak'
sed: can't find label for jump to 'ak'

scasey · 07-03-2019, 01:33 AM

Show us the source file...template.txt?

We can’t help without complete information.

pan64 · 07-03-2019, 02:58 AM

you might want to use shellcheck to check your script.
Without exact information hard to say anything.

rtmistler · 07-03-2019, 06:37 AM

Quote:

Originally Posted by chinna448

My script is something like below to replace port in the file template.txt and rename as test.txt. This script is named as test .sh

Do not name files or scripts with the name test. It is a built-in bash command. Credit to rknichols for that knowledge, because I made the exact same mistake just a short while ago.

Quote:

Originally Posted by chinna448

[/code]#!/bin/bash   [/code]

What are these garbage characters at the end of every code line? They should not be there.

scasey · 07-03-2019, 11:44 AM

Quote:

Originally Posted by rtmistler

What are these garbage characters at the end of every code line? They should not be there.

I'm not seeing that, but given the OP is talking about a "notepad" file, I'd suspect DOS line ends, which would, of course, mess up things on Linux.

grail · 07-03-2019, 09:16 PM

Here are some points to help us:

1. Please use [code][/code] tags around your code

2. As you have mentioned "notepad", please advise if any files used (script or files being read) were written under a Windows environment?

3. As advised by pan64, please use shellcheck on your script to find any basic error (such as the missing quotes from filename="test.txt)

Please update question once above have been performed

MadeInGermany · 07-04-2019, 04:36 AM

Code:

sed -i.bak "s/port/$port/g" $filename

is correct.
But I guess you did

Code:

sed -i bak "s/port/$port/g" $filename

and that's something totally different:
Now bak becomes the sed code, causing the said error message.

BW-userx · 07-04-2019, 08:41 AM

quoting is wrong.
test file says,

Code:

pea green soup

sed says,

Code:

$ var=red
$ sed  's|green|'$var'|g' testfile
pea red soup

to get sed to actually change the file itself, rather than show you the results on the cli, add your -i

Code:

sed -i 's|green|'$var'|g' testfile

Single quotes all around. That is the way I've always done it.

For the others, he said notepad file. being the txt to denote a notepad file.

OP:
If you are looking for the word(s) 'port=??' and want to replace it with 'port=80'.

Code:

#!/bin/bash

filename="testfile"
Template="template.txt"
port="port=80"

#test for files presents before issuing commands on it. 
[[ -f "$Template" ]] &&
     { cp "$Template" "$filename" ;
      sed -i 's|port.*|'$port'|g' "$filename" ;
       cat "$filename" ; }
#cat can be used for testing purposes to show results.

    read -p "Do you want to make this your file? " ans
	
    [[ "${ans,,}" = 'y' ]] && 
        { echo "Otay.. changing it to template file" ; 
	 mv -v $filename $Template ;
	 echo " done deal..." ; } ||
     { echo "OTay, not doing that..." ; }