Re: procServ softIOC server - V2.6.0 released

[Pavel Maslov <pavel.masloff@gmail.com>]

Ok. Answering my own question. The answer is:

( echo -e \\0030; sleep 1 ) | telnet localhost 2222

Regards,
Pavel Maslov, MS

oPAC fellow at Cosylab

On Mon, Feb 24, 2014 at 4:32 PM, Pavel Maslov <pavel.masloff@gmail.com> wrote:

Hi Ralph, do you know how can I automatically restart a procServ child from a command line:

I tried this and it doesn't work:

[pmaslov@localhost ~] $ echo -e \\0030| telnet localhost 2222

Regards,
Pavel Maslov, MS

oPAC fellow at Cosylab

On Mon, Nov 12, 2012 at 5:58 PM, Ralph Lange <Ralph.Lange@gmx.de> wrote:

Hi Mark,

On Mon Nov 12 2012 17:14:03 GMT+0100 (CET), Mark Rivers

<rivers@cars.uchicago.edu> wrote:
> I installed procServ 2.6.0 because I really want to use the timestamp feature on the log files.  One important application for us is using procServ to run the "telnet" command to our terminal servers connected to the VME console port on vxWorks IOCs.  This allows multiple users to connect to the VME crate, and produces nice log files.  That vxWorks output previously had no timestamps, so it was hard to know when errors occurred.

For this situation, conserver [1] is a *much* better suited application.
(Which also does nice timestamps.)
But, however, procServ should be able to handle it.

> However, procServ 2.6.0 seems to have a number of problems.
>
> - The command to exit procServ no longer appears to be configurable.  Previously it could be configured with -Q.  Now it appears to be hardcoded to be ^Q.  However, ^Q is needed when logged into a vxWorks system for XON/XOFF control (type ^S to suspend output, ^Q to resume).  We were previously setting -Q to ^E.

This option never existed in the official procServ sources.
Also, the ^Q (quit) character is only caught and interpreted when the
child process is down, i.e. when you are not connected to the remote
vxWorks system. While the child is alive and you are connected, ^Q will
be forwarded to the child process.
Which means the -Q option, that never existed, does not seem necessary
in the first place.

> - The timestamp output is totally mixed in with the output, making it very difficult to read (see below).

I will look into this.
Which platform are you running procServ on?

> - The log file has ^M characters in it at the end of each line.  This is not a new problem, 2.4.0 also had this problem.

The ^M characters look like being part of a telnet protocol.
I suspect this is an issue with the connection between the telnet client
(that you start as procServ child) and the terminal server on the other end.
Which would place it outside the scope of procServ.

Can you test with a simple non-telnet client (e.g. a shell)?

Thanks,
~Ralph

[1] http://www.conserver.com