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'm don't know how to enable auditing. Would it be appropriate to explain that in this forum? I hope so. I tried downloading filemon.exe and ran that. I've been quite successful at using this utility to diagnose other problems. However, this time, filemon did not give me any clues. It shows explore.exe accessing the temp directory but nothing else. It looks like windows explorer is just refusing to remove the readonly attribute. I used a cmd.exe (command prompt) and set my default to /program files/cvsnt. Much to my surprise, the attrib command did not show it to be readonly! Then I used the "attrib -r" command to remove the readonly attribute and received no error message! Hmmm.... Strange! I then set my default to the temp directory and tried to create a temporary file with the edit command. No problem. I use the type command to display the contents of the newly created file: again, no problem. Well, I go back to windows explorer and the "readonly" check box is solid green. I think it is lying. I'm still getting the same error messages when I try to do anything (except login) with cvs, however. Got any more ideas? Siegfried -----Original Message----- From: Peter Crowther [mailto:Peter.Crowther at melandra.com] Sent: Thursday, September 09, 2004 9:25 AM To: Siegfried Heintze; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: RE: [cvsnt] Re: cvs [server aborted]: can't create temporarydirectoryC:\Program Files\cvsnt\Temp\cvs-serv724: Permisssion Denied > From: Siegfried Heintze [mailto:siegfried at heintze.com] > It seems that someone (or, more likely, something) is > changing that temp folder to readonly. Enable auditing of filesystem events and turn on auditing of permission changes in that directory and its subdirectories. Wait for this to happen again, then examine the audit logs. You'll soon find the culprit! (This is one of the very few features that Windows NT has had for years and many UNIXes haven't that I actually think is worth it!) If you need to examine this at an even lower level, download filemon from http://www.sysinternals.com/ and keep it running for the same time. You'll get masses of output - it's worth restricting filemon to look at the smallest possible piece of filestore - but, again, it usually gets its man. - Peter