Re: rsync-2.5.0 getaddrinfo in AIX4.3?
On Tue, Dec 18, 2001 at 03:53:07PM +, Terry Raggett wrote: > Anyone have problems with getaddrinfo under AIX4.3? I have built 2.5.0 under > linux, HP and VPP without too much in the way of problems. However, AIX4.3 > version builds OK but doesn't execute getaddrinfo correctly. What error do you get? I just build the latest CVS on AIX 4.3.2 and Solaris 8/SPARC And did a transfer from AIX->Solaris with no problems. -- albert chin ([EMAIL PROTECTED])
Re: RSYNC: Backup Solution thoughts...
First: yes, wide open. Second: Sure, if your network is secure. I initially didn't understand that you were going to limit access. Anyway, trusted host access is a vulnerability. You know your system and situation. Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me Tim?" Philip Mak <[EMAIL PROTECTED]> 12/18/2001 04:50 PM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: <[EMAIL PROTECTED]> Subject:Re: RSYNC: Backup Solution thoughts... Classification: If I understand correctly, you're saying that if someone manages to gain access to my rsync server, they can read my password files and private keys, right? How would they accomplish gaining access to my rsync server, though? Only my backup server would be authorized to connect to it... I think I *do* want to back up /etc/shadow actually, because this is a full system backup that's meant to be able to be used to restore the system in case of hard drive failure. If I didn't include /etc/shadow, then everyone would lose their passwords. On Tue, 18 Dec 2001 [EMAIL PROTECTED] wrote: > readonly full disk. > rsync yourhost::rootmodule/etc/shadow . > satan -f ./shadow > telnet yourhost > login as user > su - > f*** you over. > > what, no telnet, only ssh? > grab an identity file and ssh in. > > yes, it's bad... at least, exclude secure areas.
Re: rsync doesn't accept commands
Tim: I'm ccing the list so they'll know what's going on, save duplicated effort, suggest other solutions, etc. ... private mail and all, but public forum... anyway, here's the deal i see there. you're telling rsync to use a password file, used for contacting a rsync server. Then, you use the syntax to use external transport. you need a double colon between the server and the module name. I assume, of course, that you have the server configured and running or started by inetd. I don't get an error using that wrong syntax - the --password-file option is just ignored, but i'm probably running a different version. It's possible something funny happenned in options processing. rsync uses something called "popt". I don't know what that means, but it works for me. does "rsync --version" work? If not, you're just plain not parsing commands. perhaps you'll see something if you trace the execution. strace in linux, i believe. Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me Tim?" Tim Shubitz <[EMAIL PROTECTED]> 12/18/2001 04:25 PM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: Subject:Re: rsync doesn't accept commands Classification: Tim, Here's what I was typing in on the "client" end: rsync -ra --password-file=/path/to/password.pass /path/to/folder/rsynced login@rsyncserver:rsyncmodule and I'd end up with rsync spitting out what would appear if you just typed "rsync". I've tried putting in the full path of "rsync" (/usr/bin/rsync) to see if that would help in any way. No luck so far. I've tried outputting errors to a file but get the same thing. No matter what I try rsync only "runs" itself without acknowledging commands. This is happening on a LinuxPPC box version 2.2.15. Both ends are running the same version (2.3.1). Doesn't really matter since the software doesn't get to the point where it could talk to another rsync process. Also, it won't work locally, same problem. Thanks for the help. Have a wonderful evening. Tim >which rsync make sure you're calling the one you think. it might be a >wrapper script or something. >failing that, can you show me an example? > >Tim Conway >[EMAIL PROTECTED] >303.682.4917 >Philips Semiconductor - Longmont TC >1880 Industrial Circle, Suite D >Longmont, CO 80501 >Available via SameTime Connect within Philips, n9hmg on AIM >perl -e 'print pack(, >19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), >".\n" ' >"There are some who call me Tim?"
Re: RSYNC: Backup Solution thoughts...
If I understand correctly, you're saying that if someone manages to gain access to my rsync server, they can read my password files and private keys, right? How would they accomplish gaining access to my rsync server, though? Only my backup server would be authorized to connect to it... I think I *do* want to back up /etc/shadow actually, because this is a full system backup that's meant to be able to be used to restore the system in case of hard drive failure. If I didn't include /etc/shadow, then everyone would lose their passwords. On Tue, 18 Dec 2001 [EMAIL PROTECTED] wrote: > readonly full disk. > rsync yourhost::rootmodule/etc/shadow . > satan -f ./shadow > telnet yourhost > login as user > su - > f*** you over. > > what, no telnet, only ssh? > grab an identity file and ssh in. > > yes, it's bad... at least, exclude secure areas.
Re: rsync doesn't accept commands
Martin, I've tried that too. rsync doesn't appear to want to acknowledge any commands sent to it. If I do as you noted rsync still comes back with the same "read me" info (what appears when you just type "rsync"). The same thing happens when I try to rsync locally. It runs but doesn't read in the commands I send. Tim >On Tue, 18 Dec 2001 16:30:54 -0600 >"Tim Shubitz" <[EMAIL PROTECTED]> wrote: > >> Hello folks, >>I've recently become an rsync user and have installed it on a >LinuxPPC box to sync up to another machine. So I set things up and went >to try and start rsync on the Linux box the software does nothing except >list the "read me" like info. The software just won't accept any >commands. I don't get a log, nothing. Any guesses? I'm stumped along >with my coworkers. Any help would be very appreciated. Have a great day! > >I'm not sure what you're trying to do... > >If you want to start the server, you need to edit /etc/rsyncd.conf and >then do > > # rsync --daemon > >If you want to access this > > rsync mymachine:: > >-- >Martin > > > > > > > > Tim ;) > >
Re: rsync doesn't accept commands
On Tue, 18 Dec 2001 16:30:54 -0600 "Tim Shubitz" <[EMAIL PROTECTED]> wrote: > Hello folks, >I've recently become an rsync user and have installed it on a LinuxPPC box to sync up to another machine. So I set things up and went to try and start rsync on the Linux box the software does nothing except list the "read me" like info. The software just won't accept any commands. I don't get a log, nothing. Any guesses? I'm stumped along with my coworkers. Any help would be very appreciated. Have a great day! I'm not sure what you're trying to do... If you want to start the server, you need to edit /etc/rsyncd.conf and then do # rsync --daemon If you want to access this rsync mymachine:: -- Martin > > > Tim ;) >
Re: -v prints directories twice
On Mon, 3 Dec 2001 12:33:56 -0600 "Dave Dykstra" <[EMAIL PROTECTED]> wrote: > Does it bother anybody else that -v prints directories twice? It first> prints all affected directories and files in recursive order and then> prints new directories again. I can't recall noticing that rsync always> did that, but I don't think it's a very recent change. Yes, that looks like a good fix. -- Martin
Re: rsync things to do soon
On Tue, Dec 18, 2001 at 11:59:17AM +1100, Martin Pool wrote: > On 6 Dec 2001, Dave Dykstra <[EMAIL PROTECTED]> wrote: > > > I still hope to write a --files-from option sometime in 2001. > > Excuse me if I've forgotten something from earlier: what happens when > the sender is remote? Do we send the contents of the file list across > along with the arguments, or does this option not work in that case, > or is the file named to be opened on the remote machine? We'll send the file list across along with the arguments and in place of the exclude list. Normally the file list is generated on the sender side and sent to the receiver, and I'm thinking that using --files-from when the sender is remote may be able to avoid sending the list back because the receiver already has it. It now looks doubtful that I'm going to get to this in 2001 as I've only got 3 working days left and have some other things I need to get done. I'll shoot for mid-January. Don't hold up a 2.5.1 release for this. - Dave Dykstra
rsync doesn't accept commands
Hello folks, I've recently become an rsync user and have installed it on a LinuxPPC box to sync up to another machine. So I set things up and went to try and start rsync on the Linux box the software does nothing except list the "read me" like info. The software just won't accept any commands. I don't get a log, nothing. Any guesses? I'm stumped along with my coworkers. Any help would be very appreciated. Have a great day! Tim ;)
Re: Rsyncd.conf
On Mon, Dec 17, 2001 at 10:47:44PM -0500, Pierre Abbat wrote: > On Monday 17 December 2001 11:17, David Nickel Jr. wrote: > > Howdy, > > I am pretty "green" with rsync so any help will be much appreciated. > > I want to mirror webserver A and webserver B. The two directories I want to > > mirror are /www/home and /www/default. I was wondering how I would set this > > up in rsycd.conf and how I would call it in a script? Thanks > > [www] > path=/www > hosts allow=webserverB > read only=no > > rsync -avuz /www/home webserverA::www/ That's only one way to do it (and it leaves out /www/default), and a lot depends on what you're trying to do. In general, I recommend if you're using a daemon and rsyncd.conf, that it's better to read from one than send from one, something like rsync -a webserverA::"www/home www/default" /www because it has some foibles when writing. If you've only got two machines involved, I recommend dispensing with the daemon and rsyncd.conf altogether and instead using a single colon to go over rsh, or if you have any security concerns use "-e ssh" to go over ssh. You shouldn't need "-u" unless you're changing both sides (and running to rsync commands, one in each direction), and that can get very tricky so if possible just make one the master. You don't want "-z" if you're going over a LAN, only if it's relatively slow link. - Dave Dykstra
Re: RSYNC: Backup Solution thoughts...
readonly full disk. rsync yourhost::rootmodule/etc/shadow . satan -f ./shadow telnet yourhost login as user su - f*** you over. what, no telnet, only ssh? grab an identity file and ssh in. yes, it's bad... at least, exclude secure areas. Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' "There are some who call me Tim?" Philip Mak <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 12/18/2001 11:51 AM To: Lachlan Cranswick <[EMAIL PROTECTED]> cc: <[EMAIL PROTECTED]> (bcc: Tim Conway/LMT/SC/PHILIPS) Subject:Re: RSYNC: Backup Solution thoughts... Classification: On Tue, 18 Dec 2001, Lachlan Cranswick wrote: > >My question is: How can I make server A give READ-ONLY rsync access of the > >entire disk to server B? > > Something similar the following in the /etc/rsyncd.conf file in the > server A might work(?) - just put a "read only = yes" in the config. > (plus retricting the hosts allow) I guess the path would be / > > path = / > read only = yes > uid = nobody > gid = nobody Wouldn't I need to put "uid = root" in order to give access to the entire file system (but read only)? Is this safe?
Re: RSYNC: Backup Solution thoughts...
On Tue, 18 Dec 2001, Lachlan Cranswick wrote: > >My question is: How can I make server A give READ-ONLY rsync access of the > >entire disk to server B? > > Something similar the following in the /etc/rsyncd.conf file in the > server A might work(?) - just put a "read only = yes" in the config. > (plus retricting the hosts allow) I guess the path would be / > > path = / > read only = yes > uid = nobody > gid = nobody Wouldn't I need to put "uid = root" in order to give access to the entire file system (but read only)? Is this safe?
RSYNC: Backup Solution thoughts...
>I'm thinking of how to backup an entire server ("server A") to a
>remote area ("server B") using rsync.
>
>My initial thought was to have a shell account on server B, then have a
>cronjob running as root on server A that uses rsync to send all the files
>over to the shell account on server B.
>
>Then I thought that this is not reliable against hackers, because if
>someone hacked the machine, he can find the cron job, get the password to
>the shell account on server B, and delete that backup.
>
>So, it sounds like server B should be the one with the cron job,
>synchronizing with server A.
>
>My question is: How can I make server A give READ-ONLY rsync access of the
>entire disk to server B?
Something similar the following in the /etc/rsyncd.conf file in the
server A might work(?) - just put a "read only = yes" in the config.
(plus retricting the hosts allow) I guess the path would be /
Would this work?
Lachlan.
motd file = /etc/motd
max connections = 5
syslog facility = local3
[mirrorserver]
comment = mirror server
path = /
read only = yes
list = yes
uid = nobody
gid = nobody
hosts allow = *.blah.com *.blogs.com
auth users = rsyncuser
secrets file = /etc/blahrsyncd.secrets
---
Lachlan M. D. Cranswick
Collaborative Computational Project No 14 (CCP14)
for Single Crystal and Powder Diffraction
Birkbeck University of London and Daresbury Laboratory
Postal Address: CCP14 - School of Crystallography,
Birkbeck College,
Malet Street, Bloomsbury,
WC1E 7HX, London, UK
Tel: (+44) 020 7631 6849 Fax: (+44) 020 7631 6803
E-mail: [EMAIL PROTECTED]
WWW: http://www.ccp14.ac.uk/
Backup Solution thoughts...
I'm thinking of how to backup an entire server ("server A") to a
remote area ("server B") using rsync.
My initial thought was to have a shell account on server B, then have a
cronjob running as root on server A that uses rsync to send all the files
over to the shell account on server B.
Then I thought that this is not reliable against hackers, because if
someone hacked the machine, he can find the cron job, get the password to
the shell account on server B, and delete that backup.
So, it sounds like server B should be the one with the cron job,
synchronizing with server A.
My question is: How can I make server A give READ-ONLY rsync access of the
entire disk to server B?
Re: using rsync with Mac OS X
So, that's one vote each for options 1, 2, and 3 ;-) I agree that the ideal implementation would support HFS+ as well as netatalk's .AppleDouble scheme, Mac OS X's ._ scheme, and MacBinary for all the rest. This can certainly be a goal of the implementation, but personally I am interested in the HFS+ on Mac OS X part of the problem. My implementation, whether it is MacBinary based or a change the the protocol, will leave room for these alternative schemes. Right now, I am thinking that MacBinary is the way to go. This doesn't give the flexibility and extensibility that a protocol change would give, but it does have the benefit of supporting existing rsync versions. Chris I., I'm not sure what you mean by "done at the Darwin level". If you mean that it should be done based on Darwin/BSD APIs and not Carbon/Cocoa APIs, then I am in full agreement with you. The calls that I'd use to access the resource fork are posix calls (essentially, it's just an open() call), although the calls to get HFS metadata are Mac OS X-specific (but not Carbon calls). Anyway, I'm still mulling all this over, so any suggestions are more than welcome. Once a path is chosen and code is written, things will be harder to change ;-) Regards, Mark. Chris Garrigues wrote: >A quick thought about implementation details: It would be nice if this were >done in such a way that if I were to rsync from a non-OSX netatalk system >onto an OSX system the .AppleDouble directories would be merged back into the >files, and conversely if I were to rsync from an OSX system to a netatalk >system the resource forks would be split into .AppleDouble directories. > >I guess this would be simplest with scheme 2 above. David Feldman wrote: >I'm not familiar with netatalk, but along a similar line, Mac OS X >stores resource forks and metadata differently on HFS+ and >single-fork volumes (such as UFS or NFS). If you copy a file from an >HFS+ volume over to a single-fork volume using the Finder it'll >split the pieces apart and save the resource fork and metadata under >variations of the original filename. I don't remember the exact >names but I think they're in the Mac OS X System Overview >document...something like ._. > >If there's a way I can help with the porting effort please let me >know. I don't know a lot about the lower-level details, but do know >C, C++, Cocoa, etc. and would be interested in looking at the >BSD-level info you have on transferring OS X files. > >As I stated in my earlier message, my primary interest is >synchronization of desktop and laptop, though backup would be >terrific too. I'm pretty sure there are a lot of OS X users out >there in need of both. I'm currently synchronizing with a shell >script that uses ditto. Chris Irvine wrote: >I would lean toward option "1" for several reasons. Primarily it >could probably inter-operate safely with non-HFS or older versions. > >How about a flag that changes the mode to detect named forks and >encode them in-line. These encoded files could be safely synced to >non-forked storage destinations or tape. A simple tag passed at the >beginning of a session could notify the destination that MacBinary >decoding could be attempted if available. > >I also understand the need for named resource files for systems like >netatalk. The problem with this is that every named fork system is >different: netatalk, Xinet, Helios, OSX Finder. This is a lot to >chew. I would rather the user post process files to get them into >the named fork method if they must. If you are going between two >systems using the named fork technique, this whole process is >unneeded. > >Option "3" might be the best. It seems to me that this could end up >requiring a lot of changes to the protocol. > >It should also be noted, that a project like this should be done at >the Darwin level. There have also been discussions on the >darwin-development list in June 01. No one really stared anything, >however they did discuss at length how access to resource forks >might be done while stying inside posix calls.
rsync-2.5.0 getaddrinfo in AIX4.3?
Anyone have problems with getaddrinfo under AIX4.3? I have built 2.5.0 under linux, HP and VPP without too much in the way of problems. However, AIX4.3 version builds OK but doesn't execute getaddrinfo correctly. Any ideas? Terry Raggett - -- +---+--+-+ | Terry Raggett | | /~~\ /~~\ | | ECMWF | e-mail: [EMAIL PROTECTED] | /\/\| | Shinfield Park| Tel:(+44 118) 949 9358 | ECMWF ECMWF | | Reading | Fax:(+44 118) 986 9450 | ECMWF ECMWF | | Berkshire RG2 9AX | Telex: (+44 118) 984 7908 | \/\/| | England | | \__/ \__/ | +---+--+-+ | ECMWF is the European Centre for Medium-Range Weather Forecasts| ++
Still some problems
Ok guys, I bieleve have my modules setup right. But when I run the command "rsync -a web1::default/ /www/default" I get the following error opendir(bin): Permission Denied opendir(directories): Permission Denied : Permission deniedo open // rsync error: partial transfer (code 23) at main.c (842) ... any suggestions David
RE: --size-only ?
> On 17 Dec 2001, "Kapoor, Nishikant X" > <[EMAIL PROTECTED]> wrote: > > > I need to skip a file if the file on destination has the same name > and > > same size as that of source. > > How would it know which file is the relevant one? > > If the changes are systematic, you might be able to run a pre or > post-processing script to move the files to the same name, then do the > transfer. > > Alternatively, have your script run rsync only on the files that need > to be transferred. [Kapoor, Nishikant] I have a remote source that generates a datafile with a new filename every hour but as it happens, misses a few during the day. I fetch these files through 'ftp' and distribute to my clients using 'rsync'. My clients would like to receive these data files iff they have not received them before i.e. these have a different filename or else they lose the original datetime stamp of these files (the files get a new stamp every time I fetch them from remote source). This is what I was hoping to use --size-only option for. Thanks Nishi
Example of use of librsync
Hi, I'm wondering if any of you have an example of use of the librsync library that I can look at... -Ken.
