BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Is the write(2) system call atomic

Subject: Is the write(2) system call atomic
From: gcmarx at gmail.com (Gordon Marx)
Date: Sat, 8 Apr 2006 17:20:50 -0400
In-reply-to: <20060408150246.7ba88dd8@gaf.blu.org>
References: <20060408160049.9E65D183B91@olduvai.blu.org> <18243.24.91.171.78.1144515052.squirrel@mail.mohawksoft.com> <20060408150246.7ba88dd8@gaf.blu.org>

On 08/04/06, Jerry Feldman <gaf at blu.org> wrote:
> One solution is to use lockf(3) or fcntl(2) as a lock.

Two notes: on Linux, lockf(3) is fcntl(2), and an fcntl(2) "lock" is
advisory, so an ill-behaved program will ignore it and write with
impunity.

Gordon
--
Gordon Marx
gcmarx at gmail.com

Follow-Ups:
- Is the write(2) system call atomic
  - From: gaf at blu.org (Jerry Feldman)

References:
- Is the write(2) system call atomic
  - From: markw at mohawksoft.com (markw at mohawksoft.com)
- Is the write(2) system call atomic
  - From: gaf at blu.org (Jerry Feldman)

Prev by Date: Unzipping a Windows executable archive
Next by Date: Unzipping a Windows executable archive
Previous by thread: Is the write(2) system call atomic
Next by thread: Is the write(2) system call atomic
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org