Experimental Physics and
| |||||||||||||||||
|
thanks for the flowers. You sure know how to make people listen to suggestions ;-) --allow I feel quite uncomfortable with adding an easy way to create a massive security hole. I thought the public read-only port was a kind of compromise. Not enough. Hm. I can see that it would be more liberal to have the users enforce their security policies, though. Would a compile-time Makefile configuration option (pro-actively enabling the "--allow" functionality) be sufficient for west coast usage and still be regarded safe enough? --watch I don't fully understand what you're suggesting. ProcServ is not starting the telnet session, you are. So -- how long should procServ wait for a telnet session to be opened before starting the child? A minute? A week? Until Election Day? How should it know that it's you connecting first and not someone else? Should it start the child and buffer the child's output until someone (possibly you) connects? How long or how much? In memory or as a file? And play it back to the first session only or to all future sessions? Anything in this "dynamic wait" direction seems to make things odd and complicated. Right now you can use the log file and/or debugging mode to see everything from the initial command. *Idea.* (Maybe this is what you meant in the first place, anyway.) What about adding a "--wait" option instead, that starts the procServ server, but keeps the child in "shut down" mode? You would have to connect by telnet and start it manually whenever you like -- same situation as if you toggled autorestart, shut the child down, and disconnected. This would actually be straightforward and fairly easy to implement. Cheers, Ralph Steve Lewis wrote: I finally got around to trying this out...it's amazing! Congratulations to Dave and Ralph. Of course, I do have 2 small suggestions, since it has been more than a week :-)
| ||||||||||||||||
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |