#111 is post protected against concurrent exexution?

[Wolfgang Rohdewald]

duply lokal post &
duply lokal post

I did not test this because independent of the result I think it would be helpful to have the documentation define the behaviour about such current execution.

Does the post script have to protect itself against this, or does duply?

Same applies for pre script.

Anyway I suppose pre_backup_post will never be atomic regarding locking - a user might expect that if not being warned.

[ede]

hey Wolfgang,

nope duply scripts are not protected from concurrent runs, duplicity on a profile is though.

if you need this feature you can easily implement these in the pre/post scripts yourself and use conditions for batch runs.

you can add a feat.req. ticket if you want, but i will close this "bug" as invalid.

..ede/duply.net

On 10.07.2017 01:06, Wolfgang Rohdewald wrote:

---

[bugs:#111] is post protected against concurrent exexution?

Status: open
Group: duply
Created: Sun Jul 09, 2017 11:06 PM UTC by Wolfgang Rohdewald
Last Updated: Sun Jul 09, 2017 11:06 PM UTC
Owner: nobody

~~~
duply lokal post &
duply lokal post
~~~

I did not test this because independent of the result I think it would be helpful to have the documentation define the behaviour about such current execution.

Does the post script have to protect itself against this, or does duply?

Same applies for pre script.

Anyway I suppose pre_backup_post will never be atomic regarding locking - a user might expect that if not being warned.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/ftplicity/bugs/111/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[ede]

On 10.07.2017 18:50, ede wrote:

Anyway I suppose pre_backup_post will never be atomic regarding locking - a user might expect that if not being warned.

what do you mean? pre_backup_post will always run in the correct order and wait for the previous command to finish to continue with the next one.

if you need conditional execution you can even use pre_and_backup_post .

..ede/duply.net

[Wolfgang Rohdewald]

I meant that the entire sequence pre_backup_post is not an atom: It is possible that other duplicity instances do things concurrently while this sequence is running. And I think this should be mentioned somewhere.

[ede]

ic, still

duply lokal pre_duplicity_post &
duply lokal pre_duplicity_post

the 2nd will fail when it reaches duplicity, as it maintains it own lockfile in the archive dir.

1.
what exactly is your worry, what do your pre scripts do that needs lockfile protection?

2.
if you provide a proper short text and suggest a good place to put it into the man page i would consider to add it.

..ede/duply.net

On 20.07.2017 09:22, Wolfgang Rohdewald wrote:

I meant that the entire sequence pre_backup_post is not an atom: It is possible that other duplicity instances do things concurrently while this sequence is running. And I think this should be mentioned somewhere.

---

[bugs:#111] https://sourceforge.net/p/ftplicity/bugs/111/ is post protected against concurrent exexution?

Status: closed-invalid
Group: duply
Created: Sun Jul 09, 2017 11:06 PM UTC by Wolfgang Rohdewald
Last Updated: Mon Jul 10, 2017 04:54 PM UTC
Owner: nobody

duply lokal post &
duply lokal post

I did not test this because independent of the result I think it would be helpful to have the documentation define the behaviour about such current execution.

Does the post script have to protect itself against this, or does duply?

Same applies for pre script.

Anyway I suppose pre_backup_post will never be atomic regarding locking - a user might expect that if not being warned.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/ftplicity/bugs/111/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/