From: Hans Reiser <reiser@namesys.com>
To: Anders Widman <andewid@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Can ReiserFS solve this?
Date: Mon, 28 Apr 2003 19:21:02 +0400 [thread overview]
Message-ID: <3EAD46DE.4060306@namesys.com> (raw)
In-Reply-To: <881620305.20030428165358@tnonline.net>
Anders Widman wrote:
>>On Mon, 28 Apr 2003 18:32:31 +0400, Oleg Drokin said:
>>
>>
>
>
>
>>>How about such a generic solution:
>>>
>>>you create /incoming/.temp (or /incoming.tmp), all the files are being writte
>>>
>>>
>>n
>>
>>
>>>there. When write is complete, you just do rename(2) from tempdir to /incomin
>>>
>>>
>>g
>>
>>
>
>
>
>>Oleg: A very good solution, except there are chucklehead admins at the
>>remote site that refuse to make changes to their end, and this solution
>>would require a change at the remote end to do a FTP rename.. ;)
>>
>>
>
>
> Which still should be less expencive than having to resort to
> making custom programs on your side. Use money as argument.. Works
> most of the time ;)
>
> //Anders
>
>
>--------
>PGP public key: https://tnonline.net/secure/pgp_key.txt
>
>
>
>
>
We can quote a price that you can use to bang their heads in with if you
want.;-)
--
Hans
next prev parent reply other threads:[~2003-04-28 15:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 14:04 Can ReiserFS solve this? Erik Terpstra
2003-04-28 14:17 ` Valdis.Kletnieks
2003-04-28 14:26 ` Erik Terpstra
2003-04-28 16:11 ` Christian Mayrhuber
[not found] ` <1742847756.20030428162843@tnonline.net>
2003-04-28 14:39 ` Anders Widman
2003-04-28 14:32 ` Oleg Drokin
2003-04-28 14:42 ` Valdis.Kletnieks
2003-04-28 14:52 ` Chris Dukes
2003-04-28 14:53 ` Oleg Drokin
2003-04-28 14:53 ` Anders Widman
2003-04-28 15:21 ` Hans Reiser [this message]
2003-04-28 15:45 ` Yury Umanets
2003-04-28 19:48 ` Soeren Sonnenburg
2003-04-28 14:53 ` Hans Reiser
2003-04-28 15:24 ` Erik Terpstra
2003-04-28 15:52 ` Erik Terpstra
2003-04-28 16:36 ` Kristian Koehntopp
2003-04-28 17:37 ` Anders Widman
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=3EAD46DE.4060306@namesys.com \
--to=reiser@namesys.com \
--cc=andewid@tnonline.net \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.