flock trouble

[Seb]

I'm trying to implement a file server using the code below. However
the locking doesn't work. I can delete while put'ing a file.

Anyone got an idea about why?

best regards,
seb


#! /usr/bin/env python

import Pyro.core, Pyro.naming
from Pyro.errors import PyroError, NamingError
import sys
import urllib
import os
import fcntl

class fileServer(Pyro .core.ObjBase):
basePath = "/home/snot/diku/dist/opg2/files_to_serve"

def __init__(self):
Pyro.core.ObjBa se.__init__(sel f)
self.basePath = self.basePath.s trip("..")
if not os.path.isdir(s elf.basePath) or
os.path.islink( self.basePath):
raise "invalid path"

def get(self, uri):
f = open(self.baseP ath + uri, 'r+')
fcntl.flock(f, fcntl.LOCK_SH)
data = f.read()
fcntl.flock(f, fcntl.LOCK_UN)
f.close()
return data

def put(self, uri, payload):
f = open(self.baseP ath + urllib.unquote_ plus(uri), 'w')
fcntl.flock(f, fcntl.LOCK_EX)
f.truncate()
f.write(payload )
fcntl.flock(f, fcntl.LOCK_UN)
f.close()

def delete(self, uri):
f = open(self.baseP ath + urllib.unquote_ plus(uri), 'w')
fcntl.flock(f, fcntl.LOCK_EX)
os.unlink(self. basePath + uri)
fcntl.flock(f, fcntl.LOCK_UN)
f.close()

try:
Pyro.core.initS erver()
daemon = Pyro.core.Daemo n()
locator = Pyro.naming.Nam eServerLocator( )
print 'Searching for Name Server...'
try:
ns = locator.getNS()
except Pyro.errors.Pyr oError, message:
print message
sys.exit(1)

daemon.useNameS erver(ns)

try:
ns.unregister(" fileServer")
except NamingError:
pass

uri = daemon.connect( fileServer(), "fileServer ")

print "The daemon runs on port:", daemon.port
print "The object's uri is:", uri

daemon.requestL oop()
except KeyboardInterru pt:
ns.unregister(" fileServer")
print "ctrl + c pressed"

[Antoon Pardon]

On 2008-09-08, Seb <se************ ******@gmail.co mwrote:

I'm trying to implement a file server using the code below. However
the locking doesn't work. I can delete while put'ing a file.

Anyone got an idea about why?

[code snipped]

As far as I understand you are writing some kind of server. What isn't clear
is whether the daemon is using threading or forking to handle multiple requests.

If I remember correctly, flock doesn't work well with multiple threads.

--
Antoon Pardon