iocLogPrefix incompatible with VxWorks logMsg

[Dirk Zimoch]

When defining a iocLogPrefix, messages generated with logMsg on VxWorks contain the prefix before and after each format specifier, including those generated by the system for thread id. No problem with errlogPrintf though.

On the VxWorks shell I do:
iocLogPrefix "[PREFIX]"
errlogPrintf "with errlogPrintf %s number %d\n", "hello",3
logMsg "with logMsg %s number %d\n", "hello",3

On the log server I see:
[PREFIX]with errlogPrintf hello number 3
[PREFIX]0x[PREFIX]574140[PREFIX] ([PREFIX]tShell0[PREFIX]): [PREFIX]with logMsg [PREFIX]hello[PREFIX] number [PREFIX]3[PREFIX]

[mdavidsaver (mdavidsaver)]

Which Base version/series are you working with?

fyi. iocLogPrefix was added in 3.15.0.1.

You might also like to test my as yet unreleased rewrite of errlog on 7.0 branch.

https://github.com/epics-base/epics-base/pull/113

[Dirk Zimoch (dirk.zimoch)]

I am working with 7.0.6, based on commit 59124459 (tag R7.0.6)
I will try your modifications.

The origin of the problem is that the code in modules/libcom/src/osi/os/vxWorks/logMsgToErrlog.cpp implements a low-level i/o write() function that is called multiple times per logMsg (once for each format and once for each literal string in between) but it calls the high-level i/o function errlogPrintfNoConsole which expects whole messages, not fragments.
Thus, not only the whole message gets prefixed but each fragment.

[Dirk Zimoch (dirk.zimoch)]

The errlog modifications do nothing for this bug.

Also, I noticed several uses of %z in your code. VxWorks does not support %z, even in version 6.9.

[mdavidsaver (mdavidsaver)]

> The origin of the problem is .../vxWorks/logMsgToErrlog.cpp

Agreed.

That said, logClientSend() in logClient.c could be made smarter and only send logClientPrefix before the first character following a newline ('\n'). This would require scanning through each message string, which would have the added (I think) benefit of prefixing every line of a multi-line message.

[Dirk Zimoch (dirk.zimoch)]

I started working on it. My approach is to accumulate the message (up to \n) in errlog.c.

[Dirk Zimoch (dirk.zimoch)]

See https://github.com/epics-base/epics-base/pull/281