From: Alex Riesen <Alexander.Riesen@synopsys.com>
To: Claus Rosenberger <Claus.Rosenberger@rocnet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file locking looks strange
Date: Mon, 9 Sep 2002 13:34:14 +0200 [thread overview]
Message-ID: <20020909113414.GH16092@riesen-pc.gr05.synopsys.com> (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 ?
read Documentation/locks.txt and Documentation/mandatory.txt.
You can also use advisory locking (man 2 fcntl, lockf), if it's
your own code.
-alex
prev parent reply other threads:[~2002-09-09 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 14:31 Claus Rosenberger
2002-09-07 22:23 ` jw schultz
2002-09-09 11:34 ` Alex Riesen [this message]
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=20020909113414.GH16092@riesen-pc.gr05.synopsys.com \
--to=alexander.riesen@synopsys.com \
--cc=Claus.Rosenberger@rocnet.de \
--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
all inboxes | Powered by JetHome®