[Monotone-devel] [bug #31017] automate stdio session does not see external db changes

Follow-up Comment #4, bug #31017 (project monotone): There is no such thing as locking against deletion on Unix. How exactly did you get into this situation, Stephen? The lua tests are supposed to only mess with databases that they create. __

[Monotone-devel] [bug #31017] automate stdio session does not see external db changes

Follow-up Comment #3, bug #31017 (project monotone): Further experiments; on Windows MinGW and Cygwin, the automate session does hold the database file locked; an attempt to delete it from another process fails. On Debian Linux, the file is not locked; deleting it from another process succeeds.

[Monotone-devel] [bug #31017] automate stdio session does not see external db changes

Follow-up Comment #2, bug #31017 (project monotone): Can we instruct the operating system to lock the opened database file somehow so it cannot be deleted / unlinked while its open? ___ Reply to this item at:

[Monotone-devel] [bug #31017] automate stdio session does not see external db changes

Follow-up Comment #1, bug #31017 (project monotone): Actually, to trigger the problem, the external process has to delete and recreate the db. For example, by running a lua test. Normal operations on a database are seen by the stdio process. __

[Monotone-devel] [bug #31017] automate stdio session does not see external db changes

URL: Summary: automate stdio session does not see external db changes Project: monotone Submitted by: stephen_leake Submitted on: Sat 11 Sep 2010 01:38:48 PM EDT Category: automati