G
George Potemkin
Guest
Really I'm trying to find out an explanation of the mystery on the client's side where the protrace files are created after hangups: community.progress.com/.../34409 I'm suspecting that the customer uses a monitor that infinitely and without pauses reads the _Connect VST and sends SIGUSR1 to the processes with the non-zero _Connect-Disconnect flag. Unfortunaly until 11.7 Progress does not reports to db log when a process gets the SIGUSR1. Since V11.7 we will get: (-----) Protrace location: /path/to/protrace. There is the undocumented PROSIGTRACE option that reports the actions of Progress process to the all possible signals. Unfortunately it does not force Progress to report about the signals it really received. Or maybe I just did not find such option.
Continue reading...
Continue reading...