Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Django updates
Home
About this group
Join this group
Message from discussion #9400: flock causes problems when writing to an NFS share
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Django  
View profile  
 More options Jan 10 2010, 1:26 pm
From: "Django" <nore...@djangoproject.com>
Date: Sun, 10 Jan 2010 18:26:40 -0000
Local: Sun, Jan 10 2010 1:26 pm
Subject: Re: [Django] #9400: flock causes problems when writing to an NFS share
Print | View thread | Show original | Report this message | Find messages by this author
#9400: flock causes problems when writing to an NFS share
---------------------------------------------+----------------------------- -
          Reporter:  mikeh                   |         Owner:  nobody
            Status:  new                     |     Milestone:        
         Component:  File uploads/storage    |       Version:  1.0  
        Resolution:                          |      Keywords:        
             Stage:  Design decision needed  |     Has_patch:  0    
        Needs_docs:  0                       |   Needs_tests:  0    
Needs_better_patch:  0                       |  
---------------------------------------------+----------------------------- -
Comment (by worksology):

 We are experiencing this same issue on our production environment, which
 uses NFS. I believe this started once we upgraded to Django 1.1, so we
 will likely rollback to Django 1.0 to avoid these fatal errors. Is there a
 possible stop-gap (patch) that could avoid this error without reverting to
 1.0? We'll be happy to be a second test case to help design a proper
 solution to this problem.

--
Ticket URL: <http://code.djangoproject.com/ticket/9400#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google