Re: Post-commit client script not running when committing files on a network drive

On 3 May 2010 17:20, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 03.05.2010 11:01, Felix Saphir wrote:
>> Robby Ceyssens schrieb:
>>> Any other ideas or should I report this as a bug ?
>>>
>>> -----Original Message----- From: Robby Ceyssens
>>> [mailto:Robby_at_Livios.be] Sent: donderdag 29 april 2010 8:59 To:
>>> users_at_tortoisesvn.tigris.org Subject: RE: Post-commit client script
>>> not running when committing files on a network drive
>>>
>>> No, the hook script is located on the local drive. The share is
>>> mapped to a drive letter.
>>>
>>> PS: The hook script doesn't run when located on a mapped network
>>> drive (I already discussed this in another thread).
>>>
>>> Robby
>>>
>>> -----Original Message----- From: Stefan Küng
>>> [mailto:tortoisesvn_at_gmail.com] Sent: woensdag 28 april 2010 21:13 To:
>>> users_at_tortoisesvn.tigris.org Subject: Re: Post-commit client script
>>> not running when committing files on a network drive
>>>
>>> On 28.04.2010 17:34, Robby Ceyssens wrote:
>>>> I configured a post-commit client script in Tortoise v1.6.8 and the
>>>>   script works fine when committing files on the local drives. When
>>>> I commit files on a network drive the post-commit script never runs
>>>> ?
>>>
>>> is the script located on the share? Or just the working copy? is the
>>> share mapped to a drive letter or are you using UNC paths to access
>>> the share?
>>>
>>> The scripts won't run on UNC paths since the windows shell execute
>>> won't allow that due to security restrictions.
>>
>> Have you tried debugging your script? I have no experience with client
>> side hook scripts, but the documentation says, the CWD is set to the
>> common root directory of all affected paths. So, if the working copy is
>> on a network share, the CWD should point there as well ... Could this
>> cause the problem you're experiencing?
>
> If it's on an UNC path, bat files won't work because the cmd shell can't
> deal with such paths. Try 'cd' to such a path and you'll see that it
> doesn't work.

He already said earlier

>>> No, the hook script is located on the local drive. The share is
>>> mapped to a drive letter.

The share is where the WC is located.

>>> PS: The hook script doesn't run when located on a mapped network
>>> drive (I already discussed this in another thread).

My suggestion is for Robby to use ProcessMonitor to try to see what is
going on on his particular system.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2602100
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].