inotifywait , file transferred multiple times causing overhead and delay

-1

Initially , file transfer used to happen using

inotifywait -m /path -e create -e modify | while read path action file; do 
 # transfer file to destination server
done

Since multiple modify events occur for a file, changed the code to monitor only close_write events

Each file will be transferred from a different server1 to /path of server2 only once
A similar code is monitoring files in server1

Now the issue is , multiple close_write events are occurring during a file transfer and a file is getting transferred multiple times

My question is do multiple close_write events happen during a file transfer?

Is monitoring moved_to events better option to close_write

How to make sure that a file is transferred only once

edited Feb 14 at 3:01

asked Feb 14 at 2:48

ram sudheer

add a comment |

-1

Initially , file transfer used to happen using

inotifywait -m /path -e create -e modify | while read path action file; do 
 # transfer file to destination server
done

Since multiple modify events occur for a file, changed the code to monitor only close_write events

Each file will be transferred from a different server1 to /path of server2 only once
A similar code is monitoring files in server1

Now the issue is , multiple close_write events are occurring during a file transfer and a file is getting transferred multiple times

My question is do multiple close_write events happen during a file transfer?

Is monitoring moved_to events better option to close_write

How to make sure that a file is transferred only once

edited Feb 14 at 3:01

asked Feb 14 at 2:48

ram sudheer

add a comment |

-1

Initially , file transfer used to happen using

inotifywait -m /path -e create -e modify | while read path action file; do 
 # transfer file to destination server
done

Since multiple modify events occur for a file, changed the code to monitor only close_write events

Each file will be transferred from a different server1 to /path of server2 only once
A similar code is monitoring files in server1

Now the issue is , multiple close_write events are occurring during a file transfer and a file is getting transferred multiple times

My question is do multiple close_write events happen during a file transfer?

Is monitoring moved_to events better option to close_write

How to make sure that a file is transferred only once

edited Feb 14 at 3:01

asked Feb 14 at 2:48

ram sudheer

Initially , file transfer used to happen using

inotifywait -m /path -e create -e modify | while read path action file; do 
 # transfer file to destination server
done

Since multiple modify events occur for a file, changed the code to monitor only close_write events

Each file will be transferred from a different server1 to /path of server2 only once
A similar code is monitoring files in server1

Now the issue is , multiple close_write events are occurring during a file transfer and a file is getting transferred multiple times

My question is do multiple close_write events happen during a file transfer?

Is monitoring moved_to events better option to close_write

How to make sure that a file is transferred only once

inotify

edited Feb 14 at 3:01

asked Feb 14 at 2:48

ram sudheer

edited Feb 14 at 3:01

asked Feb 14 at 2:48

ram sudheer

edited Feb 14 at 3:01

asked Feb 14 at 2:48

ram sudheer

asked Feb 14 at 2:48

ram sudheer

asked Feb 14 at 2:48

ram sudheer

add a comment |

0

active

oldest

votes

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500533%2finotifywait-file-transferred-multiple-times-causing-overhead-and-delay%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

0

active

oldest

votes

0

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu