BugCast BBC#5068: Run Double Run!

[p...@citylink.dinoex.sub.org]

Hello all,

   and welcome to the BugCast of today!

This is about running. Usually most problems are about something *not* running. This is about something running. Specifically, about running twice.

Imagine you create a Copy job. Then, within that Copy job, You can have a RunScript stance. You can obviousely not run-on-client (because the Copy job doesn't connect to the client, such a RunScript will be silently ignored - not really a good solution), but You can RunScript on server.

Then, such a RunScript will be run for the Copy Job, and then again for every Job that gets copied, as this is done with a cloned Copy Job.

Then, within the RunScript stance, you can have one or more Command= stances. And these Command stances, each of them will then run Unix programs or shell scripts. 

Only there is a problem: the *first* of those Command= stances (or the single one if there is only one) will be run TWICE only when this is a Copy job, only in the cloned instances that do actually copy a job (not on the originally invoked Copy job), and only if the RunScript RunsWhen=After - but then for each RunScript stance in the Copy job where this is true.

So this is our Bug of today, have fun with it and stay tuned for the next BugCast!

----------
Footnotes:
 * Bug numbers have been randomized for security reasons.

[p...@citylink.dinoex.sub.org]

Ups, forgot the workaround...

It is, as You can easily imagine, like this:

Job {
  Type = Copy
  ...

  Run Script {
    Runs On Client = no
    Runs When = Before
    Fail Job On Error = yes

    Command = "true"              # NOOP!

    Command = "sh -c \"/ext/libexec/Bareos/Migr... whatever \""
  }