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.
Normal users do *not* have permission to use cmd.exe on Windows 2003.
So you have to put something else into your loginfo script besides just
these commands.
Every command that looks like a shell command will start a cmd.exe
session.
Compile a program that does what you want and put it into a folder with
global access instead.
Then run it from loginfo like this:
ALL c:/data/scripts/mybugzillareporter.exe %{sVv}
If this does not work then copy your system32/cmd.exe to your CVSNT
program folder and set the permissions on this copy to allow execution
by everybody. CVSNT will then probably find this cmd.exe before the
system one.
Best regards,
Bo Berglund
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Evan Chou
Sent: den 18 november 2005 13:39
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] cvs server : cannot write entry to log filter
Hi all,
I'm running cvsnt on Windows 2003. cvsnt is installed by an non-admin
domain account named "cvsadm".
My customization is using logInfo to update Bugzilla database.
All (echo %{sVv} & more) | logInfo.bat
But it works only when cvsadm commits. When I commit CVS via other
domain users, I always get an error message "cannot write entry to
log...".
However, the file is committed indeed.
Every domain user can read/write CVS repository and can read the path to
cvsnt.
Anyone have idea to this problem?
_______________________________________________
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