Jeremy Allison wrote:
On Tue, Apr 12, 2005 at 11:58:40AM -0400, Nathan Vidican wrote:You might want to take a look at these two Microsoft Knowledge Base articles:
Since applying the two patches you emailed me (one for cpu load, one for MS Excel issues):
All is working fine now except MS Word; don't know if it's entirely related or a separate issue all together, but figured I'd post the details and see if you can think of anything; here's the behaior:
Word (apparently) creates a "~384somerandomnamefile.tmp" when a user saves, the actual file they opened goes to 0 bytes, their smbd process goes to 100% CPU load, MS Word locks up. We forcefully kill their smbd process, rename the ~whatever.tmp file to their original whatever.doc file, restart their PC (else word acts up stupid), and we're good to go... Until the next time it happens.
Apparently random files, and varyinf users/network segments as before.
Excel, powerpoint, etc not locking up nor causing similar issues at all
anyore - just MS Word. I think it might have something to do with the
autosave feature, or some sort of option in word making it create/deal with
the tmp files but I really don't understand or know the bahavior well enough
to fix it entirely on my own. Help?
Can you get me a debug level 10 log on this ? I'm currently working on ACL behaviour with MS-Office.
Jeremy.
"Long delay in the display of file names from the "Open" dialog box in Office XP"
http://support.microsoft.com/kb/818792
"The File Open dialog box does not automatically select the first available document in an Office 2003 program"
http://support.microsoft.com/kb/832889
I don't know exactly what your problem is, but the above articles may keep you from chasing the wrong horse. :-)
~Jonathan Johnson Sutinen Consulting, Inc. [EMAIL PROTECTED]
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
