-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expected Behavior? #25
Comments
Hello Tennis, Yes, this is expected as rsync will fork itself several processes. When you use "-n 8", you start 8 rsync master processes in parallel ; then rsync does what is has to do and may fork other children processes. You can examine parent/children processes' relationship with tools such a pstree (on GNU/Linux) or ps' option "-d" on FreeBSD. On my system (FreeBSD), it gives the following :
and we can see that each master rsync has forked 1 or 2 children. Best regards, Ganael. |
Perfect! Thank you, sir. |
Hi Ganael,
I'm starting FPSync like this (notice I'm asking for 8 threads):
/bin/sh /usr/bin/fpsync -O -x .glusterfs -x .root -x .r00t -n 8 -vvv /images_ebs /images
But when I do
ps -ef | grep fpsync
, I see 24 rsync processes.Is this expected behavior? What does the
-n 8
really signify?Thanks,
-Tennis
The text was updated successfully, but these errors were encountered: