On Wed, 25 May 2016 09:37:57 -0700 (PDT)
Sandor Hadas <sandorhadas...@gmail.com> wrote:

> && on that one does not help when running from cron (read the
> comments on the stackoverflow thread as it is explained there).

The rules shell executes its pipelines do not depend on cron or whatnot.
If that does not help, you have an error somewhere else.

You know, you're not the first person to run `git clone` as a part of a
cron job, so if `git clone` would really spawn detached processes and
would not wait for their completion (but why would it, really?) that
would have been detected multiple times by now, reported and fixed.

> wait is not helping either as it is per PID and the detached
> processes spawned by git clone run under different PIDs, so parent
> exits and there is no notification on child processes anymore.

RTFM.  Specifically the last sentence in this citation:

| ~% help wait
| wait: wait [-n] [id ...]
|    Wait for job completion and return exit status.
|    Waits for each process identified by an ID, which may be a process
|    ID or a job specification, and reports its termination status.  If
|    ID is not given, waits for all currently active child processes,
|    and the return status is zero.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to