search for: procmon

Hello Jeremy, > OH - that's *really* interesting ! I wonder how it is > changing the SMB3+ redirector to do this ? It looks like applications could do something and give a hint to SMB3+ redirector, so far not quite sure how to make it, per process monitor (procmon) could show that write I/O size seems could be pass from the application layers, (https://learn.microsoft.com/en-us/sysinternals/downloads/procmon) this is a example for writing, using applications (Fastcopy.exe, explorer.exe, and robocopy.exe) to transfer a file named '1GB.img' from loc...

On Fri, Aug 18, 2023 at 04:25:28PM +0000, Jones Syue ??? wrote: >Hello Ivan, > >'FastCopy' has an option to revise max I/O size and works for SMB :) >it is a tool for file transferring and could be installed to win10, >download here: https://fastcopy.jp/ > >This is an example for writing, a job would write a file named '1GB.img' >from a local disk

...internally > inside VS), or if the file-copy is being prevented by something in my > environment (files are marked writable, I already checked). The MSBuild infrastructure isn't used by VS 2005 for C++ projects; rather, VCBuild does the work. I'm not sure about VS 2008. FWIW, I used ProcMon to diagnose file-handling issues I had in my build: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx -- Barry -- http://barrkel.blogspot.com/

...via samba wrote: >> OH - that's *really* interesting ! I wonder how it is >> changing the SMB3+ redirector to do this ? > > It looks like applications could do something and give a hint to SMB3+ > redirector, so far not quite sure how to make it, > per process monitor (procmon) could show that write I/O size seems > could be pass from the application layers, well, sure, the application layer drives IO with the IO size it chooses. But when the application layer issues IOs larger then the maximum IO size allowed by SMB (8 MB iirc), the Windows SMB kernel client will...

...>>>OH - that's *really* interesting ! I wonder how it is >>>changing the SMB3+ redirector to do this ? >> >>It looks like applications could do something and give a hint to SMB3+ >>redirector, so far not quite sure how to make it, >>per process monitor (procmon) could show that write I/O size seems >>could be pass from the application layers, > >well, sure, the application layer drives IO with the IO size it >chooses. But when the application layer issues IOs larger then the >maximum IO size allowed by SMB (8 MB iirc), the Windows SMB...

...9;s *really* interesting ! I wonder how it is >>>> changing the SMB3+ redirector to do this ? >>> >>> It looks like applications could do something and give a hint to SMB3+ >>> redirector, so far not quite sure how to make it, >>> per process monitor (procmon) could show that write I/O size seems >>> could be pass from the application layers, >> >> well, sure, the application layer drives IO with the IO size it >> chooses. But when the application layer issues IOs larger then the >> maximum IO size allowed by SMB (8 MB...

...ng to be moderated because I don't > post > enough -- so then I have to wonder if my post will even see the light > of day. > It's a real pain. > > But that's getting to be an old topic .... > > Check out 'wireshark' and the sysinternals utils like 'procmon' and > 'process explorer'. > Procmon will let you monitor processes -- wireshark can let you see if > your client is waiting > for network messages... > > If you know the linux utils, cygwin is a complete set -- I use it's > 'X' server all the time to...

...argets 32-bit by default). Hooray! The missing piece that I had to track down is why I would see `deps = msvc` stuff spewing onto my terminal, rather than consumed properly by ninja. I noticed that in rules.ninja, CMake had generated: msvc_deps_prefix = LINK : error LNK2001: After some hunting in procmon, I found that there was a call to clang-cl done during the configure process that *wasn't including -m64*, leading to a link error. The text of the link error was then being interpreted as a valid output for setting msvc_deps_prefix. Attached is a quick hack patch for CMake that fixes the issu...

Hello, I run Samba 4.0.0-168.fc18.rc5.x86_64 on my Linux box. I use an editor on my Windows box to edit files on one of the Samba shares and that editor has a file update detection mechanism, polling every x seconds for changes to file modification timestamp. And around every 12 to 14 seconds it pops up the files have been changed while they aren't. Any idea what may cause this? Kind

...eresting ! I wonder how it is >>>>>changing the SMB3+ redirector to do this ? >>>> >>>>It looks like applications could do something and give a hint to SMB3+ >>>>redirector, so far not quite sure how to make it, >>>>per process monitor (procmon) could show that write I/O size seems >>>>could be pass from the application layers, >>> >>>well, sure, the application layer drives IO with the IO size it >>>chooses. But when the application layer issues IOs larger then the >>>maximum IO size allo...

..., that no longer opens the file. I've done some poking around and discovered that if I set the execute bit on the files, then everything works. That said, I'd rather not set the execute bit on entire swaths of directory trees, and this didn't seem to be an issue under Samba 3. I used Procmon.exe to confirm that cmd.exe is definitely requesting Execute/Traverse on the file and that the response is failing. This behavior also has interesting impacts on *.BAT files. If I don't set the execute bit (and I'd rather not, since I don't want Unix attempting to execute those files)...

> This can be considered good news. You have just successfully performed > the job that is normally done by R CMD SHLIB when installing source > packages or running inline C++ code. The environment variables, at > least inside your running R session, are completely fine. > > Now we need to find out why R CMD SHLIB itself fails without producing > any output. Do you get any

> The Linux client is asking for SMB1 and using 1MB write sizes. > > The Windows client is using SMB2 and *NOT ASKING FOR LEASES*. > > This is why the performance is terrible. Because the file > as no lease, the Windows redirector must pass every single > WriteFile() system call onto the wire, no matter how small > the size. > > If you can get the Windows SMB2 client

Hello, For several years I've been experiencing an intermittent Samba error when running a very intense, highly parallel build/compile jobset. A file is reported as "not found" even though it most certainly exists and re-running the compile jobset always succeeds. Samba version is 3.6.4 running on CentOS 5.8 with 64-bit kernel 2.6.18-308.4.1.el5. Windows side is 64-bit Window

OK, a couple of things aren't parsing here. > When config.h.in is hit in the build of configure the configure > project, > the configure.h file from the win32 directory is copied to main > llvm\Config\Config.h. The script in the sln file is: > There is no "configure.h" file from the win32 directory; there is a config.h, and it's 600 bytes long, compared to the

>There's a config.h file in the win32 subdirectory that implies that it's >supposed to be concatenated as part of the build process, but it doesn't >seem like that's happening from within the .sln script--am I missing a >pre-build step someplace? When config.h.in is hit in the build of configure the configure project, the configure.h file from the win32 directory is

Hi, I wrote a little "hello world" script and I am a little concerned by execution that hangs for long periods of time. *computer:* Windows XP Professional Service Pack 3 Intel(R) Xeon(R) CPU W3550 @ 3.07GHz 3.07GHz, 3.50 GB of RAM *init.pp:* class hello { notice(''Hello world!'') } *command line:* puppet apply --debug -e ''include hello''