You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
This is not really a problem, but a feature request for prsync.
rsync allows for the following options, but prsync doesnt (from what I can
tell):
--exclude=PATTERN exclude files matching PATTERN
--exclude-from=FILE exclude patterns listed in FILE
These options would allow greater flexibility when managing different types
of servers from a central location. There is definitely a workaround for
this, but requires an extra rsync. It would great to have it built in
directly in the prsync utility.
Sorry, I am not sure if this should go here, but I did not see a feature
request section.
Great utility! Thanks.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
1.4.3
Please provide any additional information below.
Original issue reported on code.google.com by NADesa...@gmail.com on 1 Mar 2010 at 8:24
The text was updated successfully, but these errors were encountered:
We've had a number of feature requests about adding support for underlying
options
for ssh and rsync. In response to this, we added new "-x"/"-X" options which
are in
the new PSSH 2.1 release. Using the new option would look something like this:
prsync -h hosts_file -x "--exclude=PATTERN" ...
Would you mind trying PSSH 2.1 and confirming that this works for you?
Thank you for your help in improving PSSH.
Original comment by amcna...@gmail.com on 1 Mar 2010 at 8:38
Thank you! This is a perfect utility for me now.
Upgraded to 2.1 and the -x option works for both --exclude=PATTERN and
--exclude-from=FILE
Much appreciated.
Original comment by NADesa...@gmail.com on 1 Mar 2010 at 11:37
Great. Since everything's working for you, I'll close this issue. Thanks for
your
participation with PSSH. Please feel free to participate on the mailing list
and/or
issue tracker if anything else comes up. Thanks.
Original comment by amcna...@gmail.com on 2 Mar 2010 at 6:12
Original issue reported on code.google.com by
NADesa...@gmail.com
on 1 Mar 2010 at 8:24The text was updated successfully, but these errors were encountered: