| *** fdrake has quit IRC | 01:25 | |
| *** cropleyb has joined #zodb | 01:27 | |
| *** cropleyb has quit IRC | 03:47 | |
| *** cropleyb has joined #zodb | 04:26 | |
| *** cropleyb has quit IRC | 06:50 | |
| *** cropleyb has joined #zodb | 08:02 | |
| *** agroszer has joined #zodb | 08:57 | |
| *** cropleyb has quit IRC | 09:32 | |
| *** cropleyb has joined #zodb | 11:24 | |
| *** cropleyb has quit IRC | 12:52 | |
| *** agroszer has quit IRC | 13:28 | |
| *** cropleyb has joined #zodb | 13:34 | |
| *** cropleyb has quit IRC | 15:09 | |
| *** namregz has joined #zodb | 15:37 | |
| namregz | hello, is it normal to have a .lock, .tmp, and .index left behind after accessing a zodb ... such as with the tutorial at readthedocs.org. | 15:44 |
|---|---|---|
| namregz | I added a db.close() and still the lock is left behind | 15:44 |
| J1m | namregz, yes. | 16:27 |
| J1m | Keeping the lock around is important for it's correct functioning. | 16:28 |
| namregz | after it's closed? after the program exits? | 16:33 |
| *** fdrake has joined #zodb | 16:34 | |
| J1m | namregz, yes | 17:29 |
| J1m | The goal of that lock is to guard against multiple processes accessing the same file. | 17:29 |
| namregz | I see, I thought when the process was done it should remove the lock ... | 17:30 |
| namregz | typical dotlock | 17:31 |
| namregz | thought wrong I guess, thank you | 17:31 |
| J1m | The lock is using fcntl-style locking. If it isn't there, there's a race condition between 2 processes creating it at the same time. | 17:38 |
| J1m | (nfc what happens on windows :) | 17:38 |
| J1m | I suppose it could be supplemented with a only-create-if-new flag, at least on posix systems. | 17:39 |
| namregz | windows ... I think that's what the CIA uses now instead of waterboarding | 17:52 |
| *** namregz has quit IRC | 19:44 | |
| *** srichter has quit IRC | 20:47 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!