topic Re: problem with sed command in Operating System - Linux

problem with sed command

praveen.. — Mon, 14 Jan 2013 04:26:40 GMT

I am facing the problem with the sed on my server.

My requirement is to change the filename in the ssort and awk scripts to point to the correct directory. To change the directory I need to delimit the “/” so as to have it “\/” in the variable to be successful with the sed.

The limitation with the ssort is it will not accept the second occurrence of the /INFILE as a variable (like /INFILE $1)

So we have to use the sed to replace the FILE_NAME after the /INFILE to point to the correct directory.

At the time of testing the sed is giving the problem.

It is successful with the command (2), but with the tilda(`) to assign it to variable it is giving the below error, command (3).

1) $ FINAL_MANUF=/apps/aloyan/loading/data;export FINAL_MANUF

2) $ echo $FINAL_MANUF|sed 's/\//\\\//g'

\/apps\/aloyan\/loading\/data

3) $ UPC_REJECT=`echo /OPT/LOYAN/LOADING/DATA_TEMP/UPC_REJECT|sed 's/\//\\\//g'`

sed: Function s/\//\\//g cannot be parsed.

is it a problem with the sed?
i tried with "sed" command with its full path "/usr/bin/sed", still I am getting the same error:
sed: Function s/\//\\//g cannot be parsed.

please suggest

P.S.This thread has been moved from HP-UX>System Administration to HP-UX > langages- HP Forums Moderator

Re: problem with sed command

RAC_1 — Fri, 05 May 2006 01:54:09 GMT

How about plain tr?

echo "/apps/aloyan/loading/data" | tr '\/' '\\' gives

\apps\aloyan\loading\data

Re: problem with sed command

Arunvijai_4 — Fri, 05 May 2006 01:57:32 GMT

Hello,

Why not this,

#echo "/apps/aloyan/loading/data" |sed 's/\/\\//g'
/apps/aloyan/loading/data

-Arun

Re: problem with sed command

Jannik — Fri, 05 May 2006 02:03:42 GMT

$ FINAL_MANUF=/apps/aloyan/loading/data;export FINAL_MANUF
$ echo $FINAL_MANUF|sed 's/\//\\/g'
\apps\aloyan\loading\data

$ UPC_REJECT=`echo /OPT/LOYAN/LOADING/DATA_TEMP/UPC_REJECT|sed 's/\//\\\/g'`
$ echo $UPC_REJECT
\OPT\LOYAN\LOADING\DATA_TEMP\UPC_REJECT

Re: problem with sed command

praveen.. — Fri, 05 May 2006 02:38:18 GMT

is this scripts related problem or "sed" command related problem?

how to resolve this?

Re: problem with sed command

Arunvijai_4 — Fri, 05 May 2006 02:51:40 GMT

Hi,

This is a script problem with usage of sed. Not a problem with "sed".

-Arun

Re: problem with sed command

Peter Nikitka — Fri, 05 May 2006 02:57:49 GMT

Hi,

your escapes via \ mus be doubled, if processing of the string is doubled:
in a plain echo '\\', in an execution in `` you have to use '\\\\'. As a side effect, echo may recognize character special sequences ('\n') you not intend to be performed.

You can do this assignment nearly without esacaping:

echo /OPT/LOYAN/LOADING/DATA_TEMP/UPC_REJECT|sed 's:/:\\:g' | read UPC_REJECT

mfG Peter

Re: problem with sed command

praveen.. — Fri, 05 May 2006 04:06:27 GMT

Hi,
I am able to get the correct output when i use the command on $ sign.

but when i create a script with the same command, it is giving the error.
sed: Function s/\//\\//g cannot be parsed.

i have changed this file permission to 777

please suggest what to do.

Re: problem with sed command

Peter Nikitka — Fri, 05 May 2006 04:09:42 GMT

Hi,

using my approach in a script (ksh, posix-shell) worked for me - which shell do you use in your script?

mfG Peter

Re: problem with sed command

praveen.. — Fri, 05 May 2006 04:11:54 GMT

I am using "ksh" shell

Re: problem with sed command

Peter Nikitka — Fri, 05 May 2006 04:50:32 GMT

Hi,

I think you did not change the vaiable assignment to this way in your script

echo /OPT/LOYAN/LOADING/DATA_TEMP/UPC_REJECT|sed 's:/:\\:g' | read UPC_REJECT

since then your original error message would not occure.
Run your script via
ksh -x scriptname
or part of it with set +x enabled before the sed call(s).

mfG Peter

Re: problem with sed command

Peter Nikitka — Fri, 05 May 2006 04:50:56 GMT

Hi,

I think you did not change the variable assignment to this way in your script

echo /OPT/LOYAN/LOADING/DATA_TEMP/UPC_REJECT|sed 's:/:\\:g' | read UPC_REJECT

since then your original error message would not occure.
Run your script via
ksh -x scriptname
or part of it with set +x enabled before the sed call(s).

mfG Peter