[cvsnt] Similar problems with temp directory creation

[Mann, Gary (London)]

Hello everyone,

I'm running 2.5.03 Build 2151 on Windows 2000 SP4. I'm experiencing the
same kind of temp directory problem that Bo was seeing, when running
pserver from any kind of client (Solaris/Linux/Windows). The default
domain name is 'EMEA'.

The symptoms are:
cvs -z9 -w -x -d
:pserver:manngar at lonis84100.uk.ml.com:/repositories/gda2 checkout -P --
gda2-all-src (in directory C:\workspaces\testcvs)
cvs [server aborted]: cannot change permissions on temporary directory
E:\temp/cvs-serv5308: Permission denied

i.e. when checking out a module from the repository

The prior "cvs login" command works fine.

If I make the user (in this case EMEA\manngar) an local administrator on
the server, everything works OK.

I've followed the previous thread on the subject, and have checked the
permissions on the temp directory. The user in question definitely has
Full Control, and this can be verified by connecting to the drive in
question as an administrator, and using the Effective Permissions tab on
a WinXP client.

I'm really stumped by this one. If I enable server side tracing I see
the following:
10:50:26: S -> CVS Server is acting as member of domain 'EMEA'
10:50:26: S -> Client sent 'BEGIN AUTH REQUEST'
10:50:26: S -> Authentication protocol returned user(manngar)
10:50:26: S -> win32switchtouser(manngar)
10:50:26: S -> win32getpwnam(manngar)
10:50:26: S -> Authenticating server: \\ELONMDCE03
10:50:26: S -> Trying Setuid helper...
10:50:26: S -> SuidGetImpersonationToken returned 00000000
10:50:26: S -> User verified - calling ImpersonateLoggedOnUser
10:50:26: S -> wnt_chmod(E:\temp/cvs-serv5308,0700)
10:50:26: S -> unlink_file_dir(E:\temp/cvs-serv5308)

If I look in the Windows event log I see a successful security logon
event:
Successful Network Logon:
 	User Name:	manngar
 	Domain:		EMEA
 	Logon ID:		(0x0,0x543E9276)
 	Logon Type:	3
 	Logon Process:	Setuid
 	Authentication Package:	Setuid
 	Workstation Name:	- 

Finally, I tried the runas suggestion. I was able to login as an admin
on the box, runas /user:emea\manngar cmd.exe, and then create a
directory in e:\temp and use cacls to modify the permissions. This all
worked fine.

So I'm stuck. Is anyone else seeing the same problems? Am I missing
something? Exactly what does wnt_chmod() attempt to perform? I notice
from the server log that there is a call to unlink_file_dir(), but no
trace message relating to the creation of the directory - is this the
problem, or is it a logfile deficiency?

Thanks in advance for any help,

Regards,

Gary
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------