Thanks for your reply, but actually I 've already used this command. My
batch file works fine when I run it mannually, but svn wait that all the
file descriptors the post-commit hook opens have been closed.
In other words "start" is the equivalent of "&" in the unix world, and I'm
looking for the equivalent of ">> /dev/null 2>&1" or anyother trick wich
allows svn to validate commit once the post-commit hook is finished, and not
once all the processes ran by it are finished.
This issue has already been discussed (see
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=53426 and
<http://svn.haxx.se/users/archive-2006-07/0421.shtml>
http://svn.haxx.se/users/archive-2006-07/0421.shtml) but no solution has
been proposed yet.
2008/6/12 Chris Lambrou <Chris.Lambrou_at_grantadesign.com>:
> Adrien,
>
> Have a look at the *start* command. You can use it to spawn a separate
> process from a batch file, in a non-blocking manner. This allows your script
> to terminate, whilst leaving the spawned process running.
>
> Chris
>
> ------------------------------
> *From:* Adrien [mailto:hannibalbundy_at_gmail.com]
> *Sent:* 12 June 2008 13:35
> *To:* users_at_subversion.tigris.org
> *Subject:* Run processes in background with post-commit hook on Windows
>
> Hi,
>
> As said in the object, I've got some difficulties on Windows to run command
> in background with the post-commit hook. Indeed there is a solution on Unix
> with the redirection of stdout and stderr (in adding >> /dev/null 2>&1 at
> the command's end), but is there any equivalent on windows ? Because adding
> 1> NUL 2>&1 is unfortunately not enough.
>
> Thanks in advance.
>
Received on 2008-06-12 16:44:43 CEST