I find the concept of having to specify a parameter like nonatomic or overwrite a bit arcane for this, as it doesn't really describe what is being done.
My gut feeling is the present behavior is acceptable, if the files were not there, ansible would need to create the file anyway, as is it's nature. On Tue, Jun 24, 2014 at 2:28 AM, Tomasz Kontusz <[email protected]> wrote: > > > Dick Davies <[email protected]> napisał: > >On 23 June 2014 19:44, Ben Hoyt <[email protected]> wrote: > > > >> I haven't dived very deep on how atomic_move is implemented, but why > >would > >> doing this change the memory requirements? > > > >Because you'd have to read in the source file to be able to 'cat' it > >into the truncated > >destination file, rather than just moving it into place > >(which requires the directory to be updated, therefore writable). > Typically you'd read a block or a few, write that, get the next one... > Repeat until end of source file. > > -- > Wysłane za pomocą K-9 Mail. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/a0e99bef-415e-4b47-91a2-8daedb9cb317%40email.android.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgwOTy8eS48Fen0Vzs7PAHae-UGSg1KmiN--%2Bs6Mp5ibHA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
