Julien LOLLIVIER
Julien LOLLIVIER
This is a good question. I have to see how procfs handles sparse files in fdinfo "pos" field, but I'm pretty sure that it will require to create a "map"...
It's the other way round, @BestPig :) Progress is currently reporting the apparent size.
The point of sparse files is to simulate a big file while actually allocating only fragments of it. If you ask the system the size of the file (stat(2)), it...
Supporting windows would probably require quite a lot of work (and maintainability issues ? will probably stay in a separate branch). And would it be really useful for this platform...
It's supposed to work as-is. What's the issue for you?
This behavior seems normal in some rsync use cases. Can you be more specific?
`progress` does not have any specific code path for specific commands, it use the same approach for each process: list opened files and report status on the "biggest" one. Looking...
`--report-biggest-n=` requires quite some changes, but hey, PRs are welcome ;) `--estimate-speed` is the default behavior of `progress`, no need for a new flag (see my original message for your...
This is a very specific situation, but we could imagine a very generic fix ("if the file is opened multiple times, look for the biggest seek").
Great idea, this is a nice addition to the project. I would like to see an OSX implementation before merging this, but I'm not excluding to merge it anyway if...