Re: [foxboro] OM programming question

> 1. For security reasons, only the program(PID) that opens the list should be
> the one that should close it. I know that OM does not protect the apps
> against this. This should be respected otherwise you may get into other
> problems.

I am attempting to close lists that were left open by FoxView process that
are no longer running.  I can close them with the omtool program ok, 
even though omtool didn't open them.
 
> 2. There are two usages of omopen/omclose; optimized and unoptimized. You
> seem to be using the optimized one. This requires that you provide the same
> size structure as the om_open call. 

This might be the problem.  I will have to check to see if I am seg faulting on
the optimized lists and not the unoptimized ones.  If so, I can create my
om structs with the same size as the list I am trying to close.  I wonder if
that is what omtool does to close these lists?

Thanks for the help Leo.
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: