Date: Sat, 30 Nov 2002 08:17:15 -0600 (CST) From: "Brian Smith" <dbsoft@technologist.com> To: "Terry Lambert" <tlambert2@mindspring.com> Cc: "current@FreeBSD.ORG" <current@FreeBSD.ORG> Subject: Re: Are SysV semaphores thread-safe on CURRENT? Message-ID: <20021130141711.CIZH19077.mailhost.chi1.ameritech.net@bbs.dbsoft-consulting.com> In-Reply-To: <3DD9D4AE.41752FF8@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Nov 2002 22:05:34 -0800, Terry Lambert wrote: >Use mmap of a backing-store file, and then use file locking to >do record locking in the shared memory segment. Ok, I did this, and it actually works considerably better than the SysV shared memory. However flock() has the same problem as the SysV semaphores, where they block the entire process, allowing the same deadlock situation to occur. Has this flock() behavior changed in CURRENT? It seems like this behavior is much more likely to change than the SysV code. Thanks! Brian Smith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021130141711.CIZH19077.mailhost.chi1.ameritech.net>