Re: [Sipp-devel] Extra CRLF when executing external commands

[<mar...@be...>]

Hello all,

I'd like to repeat a mail of mine I sent one month ago, that is
certainly related to the same problem.

Scripts worked fine in older versions of sipp, all under linux
slackware, compiled locally.

If Monica's investigation is right, it seems we have two problems: first
of all the fact that there is an end of line too much, and second, what
I noticed, the \r that should normally not occur in any unix-execution
at all, giving the weird results.

If anybody could give an answer to the last questions (changes in that
area), I can compile some versions before/after to check where it comes
from (I didn't find it looking at the code).

  Best regards,

  MarcVD

------------------------------------------------------ my mail of May 7
----------------------------------------------------------

subject: trailing control-M at end of unix command in version 2.0

Hi all,

I just downloaded the new version 2.0 and ran one of my scripts with it
(on slackware linux).

My scripts generate syslog messages using something like:

<exec command=3D"logger -p user.err -t loadI 'TIMEOUT ...[field0]...'"/>

Running these scripts with the new SIPp version 2.0 gives in the log
file a line ending in ^M (as two characters, trailing control-M
translated by syslogd).

This trailing control-M is probably there for all external unix
commands.

In version 1.1rc8 it was still OK, so I think somewhere somebody touched
this not so long ago.=20

Anybody knows what related changes happened between version 1.1rc8 and
2.0, so we could try to trace this back?

---------------------------------------------------------------------
end of mail
--------------------------------------------------------------------