Experimental Physics and
Industrial Control System

Ralph Lange <[email protected]> · Tue, 21 Sep 2010 10:10:36 -0400

 Hello Dmitry,
On 21-Sep-2010 06:50, Dmitry Teytelman wrote:

Hello Ralph,
On Mon, Sep 20, 2010 at 10:23, Ralph Lange<[email protected]> wrote:

It would be great if you opened a bug report [...]

Done (with a patch).

Great, thanks a lot!!
Also, is there any particular reason to not run the IOC inside a wrapper
like procServ [2]? That would remove the need to use nohup in the first
place.

I've learned of procServ fairly recently and have not had a chance to
investigate it in depth. Overall, since nohup does (or at least used
to do) exactly what's needed, I've looked no further. Application in
question does not tolerate IOC restarts, so if the IOC dies for any
reason we want to know about it. I understand that procServ is very
powerful and flexible, but there so many other problems to work on :(

That's fine, of course. Just wanted to know your motivation.

The two main things that procServ would give you in this case are access
to your IOC console through telnet (while it's running), and logging the
console output to a file (to find out why it died). Auto-reboot is
configurable.

</advertisement>
Cheers,
Ralph

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System