Re: rsync-2.5.6 build on Red Hat 8.0 fails
Green, Paul [EMAIL PROTECTED] said:
Horst,
Would you mind taking a look at the other spec files, specifically the
RedHat 5.0 and 7.1 files? Looks to my untrained eyes that some of the
changes you made here should be made in them as well.
For 5.0 I'm not sure, for 7.1 it certainly is applicable. In any case, I
only have a RH 8.0 system ad hand, so... In any case, the lsb .spec file
should be quite portable after my patch, so you could just delete the
others. Or you would have to add directories for the several RH releases in
between/after (* shudder *).
A full patch (all three files, lsb again as before) follows. Or keep the
other patch and rm -rf packaging/redhat, expecting people running into
trouble to fix the spec file by themselves. I added a note for them to
INSTALL. Perhaps you should contact the Debianites to contribute their
configuration scripts too?
--- rsync-2.5.6/INSTALL.orig2002-03-27 06:10:44.0 +0100
+++ rsync-2.5.6/INSTALL 2003-01-30 11:11:11.0 +0100
@@ -19,6 +19,11 @@
useful, but it should be turned off for production builds.
+RPM NOTES
+-
+
+Under packaging you will find .spec files for several distributions.
+
HP-UX NOTES
---
--- rsync-2.5.6/packaging/lsb/rsync.spec.orig 2003-01-28 06:28:35.0 +0100
+++ rsync-2.5.6/packaging/lsb/rsync.spec2003-01-30 10:42:12.0 +0100
@@ -21,7 +21,13 @@
this package.
%changelog
-* Mon Sept 11 2000 John H Terpstra [EMAIL PROTECTED]
+* Tue Jan 26 2003 Horst von Brand [EMAIL PROTECTED]
+ Fixed Sept date in %changelog here
+ Use %{_mandir} to point at manpages
+ Some distributions compress manpages, add '*' to cover this
+ Add doc/README-SGML and doc/rsync.sgml to %doc
+
+* Mon Sep 11 2000 John H Terpstra [EMAIL PROTECTED]
Changed target paths to be Linux Standards Base compliant
* Mon Jan 25 1999 Stefan Hornburg [EMAIL PROTECTED]
@@ -62,23 +68,25 @@
%setup
%build
-./configure --prefix=/usr --mandir=/usr/share/man
+./configure --prefix=/usr --mandir=%{_mandir}
make CFLAGS=$RPM_OPT_FLAGS
strip rsync
%install
-mkdir -p $RPM_BUILD_ROOT/usr/{bin,share/man/{man1,man5}}
+mkdir -p $RPM_BUILD_ROOT/usr/bin
+mkdir -p $RPM_BUILD_ROOT/%{_mandir}/man{1,5}
install -m755 rsync $RPM_BUILD_ROOT/usr/bin
-install -m644 rsync.1 $RPM_BUILD_ROOT/usr/share/man/man1
-install -m644 rsyncd.conf.5 $RPM_BUILD_ROOT/usr/share/man/man5
+install -m644 rsync.1 $RPM_BUILD_ROOT%{_mandir}/man1
+install -m644 rsyncd.conf.5 $RPM_BUILD_ROOT%{_mandir}/man5
%clean
rm -rf $RPM_BUILD_ROOT
%files
%attr(-,root,root) /usr/bin/rsync
-%attr(-,root,root) /usr/share/man/man1/rsync.1
-%attr(-,root,root) /usr/share/man/man5/rsyncd.conf.5
+%attr(-,root,root) %{_mandir}/man1/rsync.1*
+%attr(-,root,root) %{_mandir}/man5/rsyncd.conf.5*
%attr(-,root,root) %doc tech_report.tex
%attr(-,root,root) %doc README
%attr(-,root,root) %doc COPYING
+%attr(-,root,root) %doc doc/README-SGML doc/rsync.sgml
--- rsync-2.5.6/packaging/redhat/5.0/rsync.spec.orig2003-01-28 06:28:35.0
+0100
+++ rsync-2.5.6/packaging/redhat/5.0/rsync.spec 2003-01-30 10:49:29.0 +0100
@@ -21,8 +21,14 @@
this package.
%changelog
+* Thu Jan 30 2003 Horst von Brand [EMAIL PROTECTED]
+ Use %{_mandir} to point to manpages
+ Support for compressed manpages (* at end catches them in %files)
+ Add doc/README-SGML and doc/rsync.sgml to %doc
+
* Mon Jan 25 1999 Stefan Hornburg [EMAIL PROTECTED]
- quoted RPM_OPT_FLAGS for the sake of robustness
+ quoted RPM_OPT_FLAGS for the sake of robustness
+
* Mon May 18 1998 Andrew Tridgell [EMAIL PROTECTED]
reworked for auto-building when I release rsync ([EMAIL PROTECTED])
@@ -64,18 +70,20 @@
strip rsync
%install
-mkdir -p $RPM_BUILD_ROOT/usr/{bin,man/{man1,man5}}
+mkdir -p $RPM_BUILD_ROOT/usr/bin
+mkdir -p $RPM_BUILD_ROOT%{_mandir}/{man1,man5}}
install -m755 rsync $RPM_BUILD_ROOT/usr/bin
-install -m644 rsync.1 $RPM_BUILD_ROOT/usr/man/man1
-install -m644 rsyncd.conf.5 $RPM_BUILD_ROOT/usr/man/man5
+install -m644 rsync.1 $RPM_BUILD_ROOT%{_mandir}/man1
+install -m644 rsyncd.conf.5 $RPM_BUILD_ROOT%{_mandir}/man5
%clean
rm -rf $RPM_BUILD_ROOT
%files
%attr(-,root,root) /usr/bin/rsync
-%attr(-,root,root) /usr/man/man1/rsync.1
-%attr(-,root,root) /usr/man/man5/rsyncd.conf.5
+%attr(-,root,root) %{_mandir}/man1/rsync.1*
+%attr(-,root,root) %{_mandir}/man5/rsyncd.conf.5*
%attr(-,root,root) %doc tech_report.tex
%attr(-,root,root) %doc README
%attr(-,root,root) %doc COPYING
+%attr(-,root,root) %doc doc/README-SGML doc/rsync.sgml
--- rsync-2.5.6/packaging/redhat/7.1/rsync.spec.orig2003-01-28 06:28:35.0
+0100
+++ rsync-2.5.6/packaging/redhat/7.1/rsync.spec 2003-01-30 10:59:12.0 +0100
@@ -21,8 +21,13 @@
this package.
%changelog
+* Thu Jan 30 2003 Horst von Brand [EMAIL PROTECTED]
+ Use %{_mandir} to point to manpages
+ Add doc/README-SGML and doc/rsync.sgml to %doc
+
* Mon Jan 25 1999 Stefan Hornburg [EMAIL PROTECTED]
quoted
case problems with dos/windows based systems.
I have asked this before once. I am getting duplicate file names generated quite regularly when I am using samba file shares (samba seems to generate either upper or lower 8.3 case names, and also allows both to exist). Basically, the name of a file should match the name of a file at the other end if they are 8.3 format and are the same when ignoring case. Long file name behaviour should be preserved as is. Is there a patch for rsync which allows for case to be ignored for 8.3 names? The only way other way I can sort this out is to run a program to clean up the 8.3 file names before trying out the rsync (i.e. convert any 8.3 names to upper or lower case). Peter -- Peter R. Tattam[EMAIL PROTECTED] Managing Director,Trumpet Software International Pty Ltd Hobart, Australia, Ph. +61-3-6245-0220, Fax +61-3-62450210 -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
RE: proposal to fork the list (users/developers)
I tend to be someone who automatically looks for trends, and the nice thing about having just one list is that it lets me know where people are having problems. Judging by the number of questions we get, one of the biggest challenges for inexperienced rsync users is knowing why a particular file is included or excluded. Way in the back of my mind I see a need for an option that, for every file included or excluded, says which rule was used to make the decision. Nice and simple. I think if the product is easy enough to use and the documentation is good enough, then one list should be fine, because the volume should be low. Getting lots of repetitions of similar questions is an indication that there are usability issues with the product. In fact, if someone has some time on their hands, it would be a fun project to pour over a year's worth of email and do a Pareto chart on the questions we've gotten. (A good undergraduate research paper topic, perhaps?) Right away such a chart would suggest development activities we could implement to improve the usability. So I'm neutral/mildly-opposed to splitting. But if we do split, don't call it rsync-technical. Call it rsync-devel or similar. I think one of the reasons samba gets non-development email on samba-technical is that the name doens't give a clue as to what the list is about. Thanks PG -- Paul Green, Senior Technical Consultant, Stratus Computer, Inc. Voice: +1 978-461-7557; FAX: +1 978-461-3610; Video on request. Speaking from Stratus not for Stratus -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
reconnect ssh connection?
has someone come up with a trick to let disconnected ssh connections be recovered without terminating and having to restart rsync (perhaps by wrapping ssh or something)? i have a very large (but pretty stable/unchanging) tree of files that i need to sync daily, at night, between two geographically different servers. i'm using rsync -avz --force -e ssh SOURCE DEST. the connection is pretty slow and quite unreliable and many times the rsync process is terminated in the middle because of disconnected tcp connection. restarting rsync would begin the process of building the filelist which is pretty slow. -- dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
need help
p1r:/special/test #rsync --stats --progress --partial --timeout=60 -atnvvvz pamirian@rsp1l::AGBEA /special/te opening tcp connection to rsp1l port 873 - this is the motd file - Password: receiving file list ... push_dir .: Permission denied (3) rsync error: errors selecting input/output files, dirs (code 3) at main.c(317) rsync: connection unexpectedly closed (136 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) _exit_cleanup(code=12, file=io.c, line=150): about to call exit(12) this is the error message Im getting when Im trying to use rsync. In the AGBEA directory all my files are directories, can this cause the problem? Ideas? Suggestions? Im running the command as root. Thanks. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
question
I run my rsync command as root and yet I cant initiate a transfer if on the source site my directory has 770 permission. If I change it to 777 the I can transfer When I run the rsync command, does it change its uid or gid to something else ..? -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Precompiled rsync 2.5.5 for SPARC Solaris 8 64bit
Hello List, Would anybody have a precompiled version of rsync 2.5.5 for SPARC Solaris 8 64bit? Thanks in advance for your help, Loris -- Loris Serena Unix Systems Administrator PaddyPower Bookmakers Phone : +353-1-4049633 http://www.paddypowerplc.com Mobile: +353-87-9683760 mailto:[EMAIL PROTECTED] Privileged, confidential and/or copyright information may be contained in this communication. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended addressee, you may not copy, forward, disclose or otherwise use this e-mail or any part of it in any way whatsoever. To do so is prohibited and may be unlawful. If you have received this email in error please notify the sender immediately. Paddy Power PLC may monitor the content of e-mail sent and received for the purpose of ensuring compliance with its policies and procedures. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: reconnect ssh connection?
Paul Haas wrote: On Tue, 28 Jan 2003, David Garamond wrote [twice!]: i'm really sorry about that. i didn't receive my own post today so i admit i acted in haste. -- dave -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync question
On Thu, Jan 30, 2003 at 12:19:22PM -0500, [EMAIL PROTECTED] wrote: When setting up rsync in daemon mode, which side do I put the daemon on? My environment is as follows: One Linux host will house the backup data files for three servers (1 SCO Open Server and 2 Solaris 8). I want to know if it is better to: 1. setup the daemon on the Linux host and push from the other 3 hosts. OR 2. setup the daemons on the 3 hosts and have the Linux box pull using rsync. Thanks for any help you can provide. It doesn't really matter as far as rsync is concerned. The system load, if that is an issue, is on the sender regardless of the client-server relationship. What you have to decide is whether to manage three rsync daemons and one initiator (cron probably) or three initiators and one rsyncd. Perhaps more of an issue is the metadata if any. When i designed dirvish i decided to pull, rather than push, because the backup metadata would only be on the backup server so it was simpler to have the backup server initiate the backups as an rsync client. If you have no metadata then i can't think of any overriding reason to pull. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: proposal to fork the list (users/developers)
On 30 Jan 2003, Green, Paul [EMAIL PROTECTED] wrote: I tend to be someone who automatically looks for trends, and the nice thing about having just one list is that it lets me know where people are having problems. Judging by the number of questions we get, one of the biggest challenges for inexperienced rsync users is knowing why a particular file is included or excluded. Yes, that's definitely a large advantage of having a single list. Way in the back of my mind I see a need for an option that, for every file included or excluded, says which rule was used to make the decision. Nice and simple. I came to the same conclusion in a similar way a while ago. If you use -vv for rsync, you should see messages about exactly this. :-) -- Martin Debian: giving you the power to shoot yourself in each toe individually. -- ajt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: reconnect ssh connection?
On 30 Jan 2003, David Garamond [EMAIL PROTECTED] wrote: has someone come up with a trick to let disconnected ssh connections be recovered without terminating and having to restart rsync (perhaps by wrapping ssh or something)? Ooh, interesting idea... You might do it with some kind of wrapper at both ends... Alternatively, by changing ssh options perhaps you can get the process to stay open even if the link goes away, by increasing timeouts and so on... -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
