From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: file locking looks strange
Date: Sat, 7 Sep 2002 15:23:51 -0700 [thread overview]
Message-ID: <20020907222350.GA24809@pegasys.ws> (raw)
In-Reply-To: <44499.213.68.24.98.1031409116.rocnet@deathstar.of.rocnet.de>
On Sat, Sep 07, 2002 at 04:31:56PM +0200, Claus Rosenberger wrote:
> How i can informations about file locking for applications.
>
> if i open a document with one application on the terminalserver and try to
> open the same document in another session i can write on the second
> session. this happens for example with openoffice. how i can really lock
> the file if one application open this doc for reading and writing ?
start with 'man -k lock|grep file' That will give you some
starting points. If you need more any book on UNIX or Linux
programming that doesn't list both methods isn't worth buying.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2002-09-07 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 14:31 file locking looks strange Claus Rosenberger
2002-09-07 22:23 ` jw schultz [this message]
2002-09-09 11:34 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020907222350.GA24809@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox