• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
file locking: fcntl vs. flock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

file locking: fcntl vs. flock


  • Subject: file locking: fcntl vs. flock
  • From: William Andrew Burnson <email@hidden>
  • Date: Sun, 31 Aug 2008 15:12:29 -0500 (CDT)

Hello,

I'm debugging someone's multiple instance preventer on Mac OS X Leopard. It operates using a file-based lock, using fcntl. However we found that this did not work in a networked environment with SMB filesystems because it returned errno 45 ENOTSUP (Operation not supported). Admin and local accounts performed the lock, but for a networked user, it failed. In a previous version, the code used flock, which does work, but apparently that isn't a general solution either because it doesn't do anything for AFP shares.

Does anyone know what a good solution would be for creating a file-based interprocess lock?
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: file locking: fcntl vs. flock
      • From: George K Colley <email@hidden>
  • Prev by Date: Re: FSCopyObjectSync and Samba, error -54
  • Next by Date: Re: file locking: fcntl vs. flock
  • Previous by thread: Re: Where is the "Ignore ownership on this volume" bit?
  • Next by thread: Re: file locking: fcntl vs. flock
  • Index(es):
    • Date
    • Thread