Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
I think that when the script is executed it gets executed in the context of the user doing the cvs operation. So the permission to use cmd.exe must be given to all of your cvs users. /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Mathew Davies Sent: den 10 maj 2005 12:47 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: RE: [cvsnt] Re: cvsnt & win2k3 script permissions > -----Original Message----- > From: cvsnt-bounces at cvsnt.org > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund > Sent: 09 May 2005 20:20 > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: [cvsnt] Re: cvsnt & win2k3 script permissions > <snip> > >So I thought I was all setup and was just adding in things like the > >postcommit > >script I discovered these don't seem to work now. This seems > to be true > >of all scripts I can call like the old loginfo and cvsnotify > scripts. > > > >I have tried temporary setting the permissions on perl, cmd.exe and > >update_websites.pl > >to read & excute. The cvs temp folder and the responsity to have > >everyone full > >control yet when I commit a file that is in a module set to use > >postcommit > >script I just get a script failed message on commit. I have > also tried > >changing the cvsnt services from system to a local user with > no affect. > > > >Does anyone know what I have to do or what permissions I set > on win2k3 > >to allow cvsnt to run scripts? Has anyone else installed > cvsnt on win2k3 > >and used scripts in things like loginfo or postcommit successfully? > > > > The problem here is the way W2003 has locked down alomost everything > on the server... > Specifically your problem comes from the way cmd.exe is locked down. > You can do one of two things: > 1) Go to %systemroot%\system32 and check the permissions of cmd.exe. > You will probably discover that it is pretty much locked down. Since > it is used to launch the scripts, you have to loosen up these > permissions. > > or > 2) You can *copy* %systemroot%\system32\cmd.exe to the install folder > for CVSNT. The copy will then not have the permissions as tightly set > and CVSNT will find it first since it is right in the same folder as > cvs.exe itself. > I have tried both option 1 & 2 if anyone have got this working what permissions did they set on cmd.exe and perl binaries and libs? are they running cvs as local system or a user? Any help is appreciated thanks mat ---------------------------------------------------------------------- This message has been scanned for viruses and dangerous content by IPT MailScanner, and is believed to be clean. Interactive Prospect Targeting http://www.ipt-ltd.co.uk/ ---------------------------------------------------------------------- ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs