[Zope] Mouting + Logging Errors after Zope Upgrade 2.7.4 --> 2.11.1

[Wolfgang Lausenhammer]

Thank you for your answer.

I just tried to lock the file manually and it works
But I recognized when zope reports those errors with locking, the reported 
file can't be opened in the filesystem also, so it is really locked. It 
seems that zope doesn't unlock it and so if zope tries to access it again 
(thus locking it again) it can't because it is locked... (I never call the 
locking-function manually)
Altough the error doesn't have any effect on the website I'm running... 
Kinda strange..

-- Wolfgang

"Dieter Maurer" <dieter at handshake.de> schrieb am 02.08.2008 09:45:50:

> 
> Wolfgang Lausenhammer wrote at 2008-8-1 09:20 +0200:
> > ...
> >__init__
> >  File "D:\zope\2.11.1\Zope\lib\python\ZODB\lock_file.py", line 42, in 
> >_lock_file
> >LockError: Couldn't lock 
> >'D:\\workspace_zope\\xla-2008/var/Stdcontainer_o.fs.lock'
> 
> A look at the code reveals:
> 
>         # Windows
>         def _lock_file(file):
>             # Lock just the first byte
>             try:
>                 msvcrt.locking(file.fileno(), msvcrt.LK_NBLCK, 1)
>             except IOError:
>                 raise LockError("Couldn't lock %r" % file.name)
> 
> Thus, your Windows operating system reported a problem
> in "msvcrt.locking". 
> 
> Emulate the operation in an interactive Python interpreter
> and more carefully look at the error indication.
> Consult your OS documentation to find out the reasons for the problem.
> 
> 
> 
> -- 
> Dieter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/zope/attachments/20080804/0d8b8d7e/attachment.html