Experimental Physics and
| |||||||||||||||||
|
Till Straumann wrote: I'm not familiar with the internals of cau. However, note that the bug I reported bites only if Ok, that explains the different cleanup behavior that I saw. I agree with your fix, which I have just committed to CVS. Another problem though appears to be that at no point does the CA client library actually fork off a caRepeater itself, even after this message appears:I'm afraid I don't understand. With caRepeater on the PATH everything works Right, if a caRepeater program is found then everything works fine; I was still testing the case where caRepeater is not in the path, and was expecting the CA client library to fork itself again and run the CA repeater code in the child fork in that case. The CA library used to do that to ensure that there would always be a repeater running when it needed one, but I think people got confused because if they didn't run caRepeater from their machine's startup the forked first client that they started would become the repeater for the machine, and they'd wonder why their MEDM or ALH or whatever program it actually was continued to run after they'd shut it down. I now vaguely remember Jeff discussing the idea of taking that behavior out, and it looks like he did, so maybe it isn't a bug after all. Thanks, - Andrew -- The right to be heard does not automatically include the right to be taken seriously. -- Hubert H. Humphrey
| ||||||||||||||||
ANJ, 10 Nov 2011 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |