rsyncopts not working as expected "-s: unknown option" where -s isn't specified- High Sierra

[Filmtangent]

Hi,

I'm trying to using parsyncfp with the following options: parsyncfp --rsyncopts='-ah' --v=2 --NP 3 /src /dest. Unfortunately when attempting to use this, I'm receiving an error that '-s' is an unknown option. This is likely due to the exclusion of the -s rsync flag in the Mac application of rsync.

I'm more wondering why I can't use rsyncopts to negate the use of -s at all. Am I mistaken in thinking that rsyncopts should disabled the default -a -s flags? Or am I simply using parsyncfp incorrectly?

Thanks

[hjmangalam]

Hi, I assume you're trying to use parsyncfp (psfp) to connect from a LInux system to a Mac..? Or is it from a Mac to a Mac? If the former, I'll have to check when I get to my office and activate my Mac. If the latter, I'm surprised that you got that far since I haven't done much to assure Mac-compatibility.

However, I can add a check to remove the -s flag if there's a mac on either end of the transfer (that option isn't mentioned in the help output, but I added it to protect filenames that contain spaces). You're right that Macs don't natively support that option (tho a Mac would be the main beneficiary of it).

Thanks for the bug report - I'll try to get back to you later today.
hjm

[Filmtangent]

Yes correct I’m attempting to use psfp. So its actually between mounted disks on a Mac (disks hosted on linux) but it should act as Mac>Mac. I edited the app to remove the s flag and ask it to use -h instead, but the desired outcome (of a progress indicated fpsync) seems to still be out of reach. Also you’re right, it would be a sensible thing for Macs to use the -s option. No rush on this. Its a nice to have for me atm. :) Thanks! On Mon, Apr 30, 2018 at 16:21, Harry Mangalam <notifications@github.com> wrote: Hi, I assume you're trying to use parsyncfp (psfp) to connect from a LInux system to a Mac..? Or is it from a Mac to a Mac? If the former, I'll have to check when I get to my office and activate my Mac. If the latter, I'm surprised that you got that far since I haven't done much to assure Mac-compatibility. However, I can add a check to remove the -s flag if there's a mac on either end of the transfer (that option isn't mentioned in the help output, but I added it to protect filenames that contain spaces). You're right that Macs don't natively support that option (tho a Mac would be the main beneficiary of it). Thanks for the bug report - I'll try to get back to you later today. hjm — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [#10 (comment)] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AJ2LYgoRr8LcvOczQIzGc81rnCkqj-hLks5ttywLgaJpZM4TsaMg] .

[hjmangalam]

OK - this will get me on the Mac to verify what works and what doesn't. Again, thanks for the report. hjm

On Monday, April 30, 2018 8:26:02 AM PDT Filmtangent wrote: Yes correct I’m attempting to use psfp. So its actually between mounted disks on a Mac (disks hosted on linux) but it should act as Mac>Mac. I edited the app to remove the s flag and ask it to use -h instead, but the desired outcome (of a progress indicated fpsync) seems to still be out of reach. Also you’re right, it would be a sensible thing for Macs to use the -s option. No rush on this. Its a nice to have for me atm. :) Thanks! On Mon, Apr 30, 2018 at 16:21, Harry Mangalam ***@***.***> wrote: Hi, I assume you're trying to use parsyncfp (psfp) to connect from a LInux system to a Mac..? Or is it from a Mac to a Mac? If the former, I'll have to check when I get to my office and activate my Mac. If the latter, I'm surprised that you got that far since I haven't done much to assure Mac-compatibility. However, I can add a check to remove the -s flag if there's a mac on either end of the transfer (that option isn't mentioned in the help output, but I added it to protect filenames that contain spaces). You're right that Macs don't natively support that option (tho a Mac would be the main beneficiary of it). Thanks for the bug report - I'll try to get back to you later today. hjm — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [#10 (comment) 0] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AJ2LYgoRr8LcvOczQIzGc 81rnCkqj-hLks5ttywLgaJpZM4TsaMg] .

Harry Mangalam, Info[1]

…

-------- [1] http://moo.nac.uci.edu/~hjm/hjm.sig.html

[rkdass]

Hi, I was wondering if you were able to confirm if parasync was compatible with a Mac (macos Catalina)? I extracted the parasync tarball and added it to my PATH. I installed a few missing dependencies such as "fpart" and "ip" (iproute2mac) using homebrew. However, I'm not sure how to proceed with installing dependencies like "ethtool" and "iwconfig". I may be wrong, but I read (please see below) that macos handles these commands differently. Would you please help point me in the right direction?

[ iwconfig on mac ]
https://apple.stackexchange.com/questions/80187/is-there-a-mac-os-x-equivalent-of-the-linux-iwconfig-command
[ ethtool on mac ]
https://apple.stackexchange.com/questions/44537/ethtool-equivalent-for-os-x-lion

[hjmangalam]

HI Rahul, I'm afraid, I've dropped the ball on getting parsyncfp to run on MacOS. It's on the list of ToDos but fairly low, especially since my access to MacOS has disappeared. Sorry

…

On Mon, Oct 19, 2020 at 6:52 AM Rahul Kumar Dass ***@***.***> wrote: Hi, I was wondering if you were able to confirm if parasync was compatible with a Mac (macos Catalina)? I extracted the parasync tarball and added it to my PATH. I installed a few missing dependencies such as "fpart" and "ip" (iproute2mac) using homebrew. However, I'm not sure how to proceed with installing dependencies like "ethtool" and "iwconfig". I may be wrong, but I read (please see below) that macos handles these commands differently. Would you please help point me in the right direction? [ iwconfig on mac ] https://apple.stackexchange.com/questions/80187/is-there-a-mac-os-x-equivalent-of-the-linux-iwconfig-command [ ethtool on mac ] https://apple.stackexchange.com/questions/44537/ethtool-equivalent-for-os-x-lion — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASF3YZQZBQVDJCDZTSZBLLSLRACRANCNFSM4E5RUMQA> .

-- Harry Mangalam