[foofus-tools] pwdump

[JC Ferguson]

I cannot recall - is pwdump caching the results locally? I seem to recall some versions doing that.  I.e., it builds up all the data in memory, then dumps to a file.  If that is the case, I can see some scale issues with 3.5 million entries in your AD, i.e., you'd eat up the memory.

When it is chugging along, have you run taskmgr, sort by memory usage, and observed who the hogs were?

-jc



> -----Original Message-----
> From: foofus-tools-bounces at lists.foofus.net [mailto:foofus-tools-
> bounces at lists.foofus.net] On Behalf Of Keith Morrell
> Sent: Saturday, May 22, 2010 18:52
> To: foofus-tools at lists.foofus.net
> Subject: [foofus-tools] pwdump
> 
> Update:  I've tried the suggestions from others in the forum and they don't
> seem to make a huge difference....but the one remaining issue is still
> happening.
> 
> On my ~3,500k AD, the program seems to die about 2.2M records through (2676
> dots), using a very rough estimate of the number of dots displayed on the
> screen/time run (from this bit of code in pwdump.cpp) - comparing this to my
> ~700k which displayed 851 dots...
> 
> else if(i % 100 == 99)
>     fprintf(stderr, ".");
> 
> So it seems it must be running out of time or space somewhere...
> 
> When it stops, the {GUID} service is still left running.
> 
> I can compile it all up now to make any other changes others might suggest.
> What would be good is a trace output maybe in LsaExt.c, or even some way of
> breaking the process up so that the extract (absolute minimum needed) is
> done to a "raw" intermediate file, and the final conversion/formatting done
> with another module??
> 
> Thanks in advance for any more help...
> 
> Keith
> 
> 
> _______________________________________________
> foofus-tools mailing list
> foofus-tools at lists.foofus.net
> http://lists.foofus.net/listinfo.cgi/foofus-tools-foofus.net