[Casa-framework] Table lock under python

[Ger.VanDiepen at csiro.au]

Wes,

In Glish every 30 seconds or so a relinquishAutoLocks was done to unlock
all open tables. That is probably hard to do in python.
I think the user has to do locking and unlocking more explicitly.
Note that it is also possible to open readonly files without locking.
The only problem with that is that if another process writes into it, it
does not get synchronized automatically.

The fact that the other ms.open waits until the first one is finished
means that ms.open opens the ms for writing. Is that really needed?

Cheers,
Ger

-----Original Message-----
From: casa-framework-bounces at donar.cv.nrao.edu
[mailto:casa-framework-bounces at donar.cv.nrao.edu] On Behalf Of Wes Young
Sent: Wednesday, 27 September 2006 11:34 PM
To: Kumar Golap
Cc: casa-framework at nrao.edu; Ger van Diepen
Subject: Re: [Casa-framework] Table lock under python

Hi Kumar,

OK, two windows,

python 1

   ms.open(msname, lock=true)

works fine....

python 2

ms.open(msname)

hangs....till python 1 exits.

OK, I'm going to see what I can find out.

wes
wyoung at aoc.nrao.edu


On 26 Sep 2006, at 23:13, Kumar Golap wrote:

> I've noticed an interesting locking issue... Maybe because now that
> the python and the table or ms tool or any other too have the same
> process id ...the lock on tables seems to hold even after quit the
> tool.  So if i access the same table via the glish table tool say it
> waits on the lock till I quit python.
>
> Kumar
> _______________________________________________
> Casa-framework mailing list
> Casa-framework at donar.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/casa-framework

_______________________________________________
Casa-framework mailing list
Casa-framework at donar.cv.nrao.edu
http://listmgr.cv.nrao.edu/mailman/listinfo/casa-framework