power cables
Dear Sir or Madam, It's an honor to know your company through the website. We are a large manufacturer of which specialize in manufacturing and exporting all kinds of power cords, plugs, cordsets, extension cords, sockets, and so on. Now we are planning to incorporate our business activities in your market, and we will be much obliged for your introduction to a most reliable importer handling this field. We've exported a large quantity of power cords to many countries, and enjoying a high reputation through excellent quality and price. We believe you have a great demand of power cords, please don't hesitate to contact us if you are interested in. Please advise us the following: 1) Cable specification: VDE approved H05VV-F, H03VV-F, H03VVH2-F, H05RN-F,¡UL approved SJT, SJTW, HPN 18AWG, 16AWG, with USA plug. 2) Length, Color, requirement of the end. 3) Which types about plug? 4) Quantity per order? Please send us the drawings for these items so that we can quote you the best offer immediately. Please transfer this letter to Purchasing Department of your company when you received it. Your kind attention to this matter will be much appreciated. With thanks and best regards, Shanghai Foundoor Electrical Co., Ltd. Steven Xu Contact information: Shanghai Foundoor Electrical Co., Ltd. Office Address: RM 204, No. 54, Lane 250, Zhenjin Road, Shanghai, China 200333 Tel: 86-21-56348070Fax: 86-21-56348069 E-mail: [EMAIL PROTECTED]http://www.foundoor.com -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
rsync with --exclude files
HI, I'm trying to exclude some files directories from a filesystem which I would like to copy to a different site. I did: # rsync -avz --exclude-file=/fs21/tmp/perl_scripts/exclude.txt /fs22/a/circuit_design mickey.willow.com:/cpu/store/design where file /fs21/tmp/perl_scripts/exclude.txt contains the following directories and files to be excluded from /fs22/a/circuit_design: # cat /fs21/tmp/perl_scripts/exclude.txt /fs22/a/circuit_design/file1 fs22/a/circuit_design/file2 fs22/a/circuit_design/dir1 I'm invoking rsync from a machine named winnie.willow.com to transfer files/directories in /fs22/a/circuit_design to mickey.willow.com:/cpu/store/design. However, it still copies all files or directories in the filesystem /fs22/a/circuit_design to mickey.willow.com:/cpu/store/design. It should not include the files/directories mentioned in the /fs21/tmp/perl_scripts/exclude.txt file. I've tried with the following for excluding just 1 file or directory and it works: # rsync -avz --exclude=/fs22/a/circuit_design/file1 /fs22/a/circuit_design mickey.willow.com:/cpu/store/design It does not however work when I did the following for excluding 1 file/directory: rsync -avz --exclude=/fs22/a/circuit_design/file1 --exclude=/fs22/a/circuit_design/file2 /fs22/a/circuit_design mickey.willow.com:/cpu/store/design I was wondering if this should be the way to rsync a filesystem, excluding some files/ directories? Please help. 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
rsync with --exclude files
HI, I'm trying to exclude some files directories from a filesystem which I would like to copy to a different site. I did: # rsync -avz --exclude-file=/fs21/tmp/perl_scripts/exclude.txt /fs22/a/circuit_design mickey.willow.com:/cpu/store/design where file /fs21/tmp/perl_scripts/exclude.txt contains the following directories and files to be excluded from /fs22/a/circuit_design: # cat /fs21/tmp/perl_scripts/exclude.txt /fs22/a/circuit_design/file1 fs22/a/circuit_design/file2 fs22/a/circuit_design/dir1 I'm invoking rsync from a machine named winnie.willow.com to transfer files/directories in /fs22/a/circuit_design to mickey.willow.com:/cpu/store/design. However, it still copies all files or directories in the filesystem /fs22/a/circuit_design to mickey.willow.com:/cpu/store/design. It should not include the files/directories mentioned in the /fs21/tmp/perl_scripts/exclude.txt file. I've tried with the following for excluding just 1 file or directory and it works: # rsync -avz --exclude=/fs22/a/circuit_design/file1 /fs22/a/circuit_design mickey.willow.com:/cpu/store/design It does not however work when I did the following for excluding 1 file/directory: rsync -avz --exclude=/fs22/a/circuit_design/file1 --exclude=/fs22/a/circuit_design/file2 /fs22/a/circuit_design mickey.willow.com:/cpu/store/design I was wondering if this should be the way to rsync a filesystem, excluding some files/ directories? Please help. 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
RE: --delete doesn't work when transferring many files
That wouldn't be a problem, because rsync generates the lists and does the compares, and if there are no errors or --ignore-errors is invoked (logical or... no errors, ignore-errors is not tested), and --delete-after is not invoked, the deletions are performed, followed by the sends. I haven't read the code, but i think that since --ignore-errors is documented as applying only to the deletion phase, i would expect that creation errors might not count against --delete. It's all clearly documented in the man page. Perhaps in his larger runs, he's running into items for which he has no write permission. Sometimes, adding --force can overcome that, though that is more commonly used to force the wipeout of a dir being replaced with a symlink. I'd suggest that he choose a filesystem with plenty of empty space to recieve a complete trace of his run, all threads (-f option to truss and strace), and less that trace, searching for unlink. Somewhere around an unlink line, he should see something that failed. Tim Conway [EMAIL PROTECTED] 303.682.4917 office, 3039210301 cell 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? Granzow, Doug (NCI) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/24/2002 01:05 PM To: 'William R. Dickson' [EMAIL PROTECTED] '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject:RE: --delete doesn't work when transferring many files Classification: Is it possible that the destination directory is filling up? I believe rsync saves deletes until the end, so that it knows there are no IO error conditions that would cause it to exit without deleting. Filling up the destination filesystem is probably one of those error conditions. Another possibility would be permissions problems on the destination preventing rsync from writing to the target directory. Try adding another v to your command line (-rtvv) to get more verbosity; rsync may tell you why it is skipping the deletes. You could add --ignore-errors to force the --delete, but I would recommend finding the cause of the problem first. -Original Message- From: William R. Dickson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 9:30 PM To: [EMAIL PROTECTED] Subject: --delete doesn't work when transferring many files This is a curious thing. I'm syncing two directories, containing some 250 subdirectories totalling around 11,000 files. This: rsync --password-file=/usr/local/etc/rsync/.passwd --delete -rtv --exclude-from=/usr/local/etc/rsync/excludes /usr/local/sourcedir [EMAIL PROTECTED]::modulename ...works fine if both directories are already nearly in sync. Deleting a few files from the source causes matching deletions on the destination. But recently I made major changes to the source directory, which should have resulted in nearly everything being deleted from the destination server. However, it doesn't -- it simply starts uploading files. If I change -rtv to -rtvn, rsync correctly reports a whole slew of planned deletions -- but as soon as I try to run it for real, it simply fails to do the actual deleting. If it helps at all, the source system is a NetBSD/MacPPC machine, and the destination is a FreeBSD/i386 machine. Any ideas? I searched the list archives and google, but was unable to find any similar issues. Thanks, -Bill -- William R. Dickson -- Consuming the Earth's limited resources since 1968 [EMAIL PROTECTED]http://www.seavoy-dickson.org/ But I'm the luckiest guy on the lower east side 'Cuz I've got wheels, and you wanna go for a ride - The Magnetic Fields -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- 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: non-interactive ssh connections (was Re: RSYNC ISSUE)
Gouri: close. Try Ssh-keygen -p -P ''. You might argue that ssh should guess that -P imlplies -p, but that's an issue for your ssh maintainer. Also: you don't ordinarily distribute the private key. You need the PUBLIC key in $HOME/.ssh/authorized_keys on any system you want to access with the private key. Maybe i'm seing your application backward, and you are creating the key on the system being accessed, and putting the private key on all the systems accessing it. Anyway, the ssh-keygen -p changes only the private key. You could actually generate a key pair, put the public key on the system you want to access, put the private key on all the systems you want to access from, run ssh-keygen -p on all those seperate keys, giving them all different passwords, and still use them all on the same public key. Tim Conway [EMAIL PROTECTED] 303.682.4917 office, 3039210301 cell 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? Kar, Gouri X. -ND [EMAIL PROTECTED] 07/24/2002 06:42 PM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: Subject:RE: non-interactive ssh connections (was Re: RSYNC ISSUE) Classification: Just tell me one thing. If I generate the key using command Ssh-keygen -P '' --- It should remove passphrase correct Is there any thing wrong from the syntax standpoint. I am working on IBM-AIX OS If you look on the details about the mail below, you will see my difficulty in executing rsync with SSH from cron. Thank you. Hope to get your response. Gs -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 3:41 PM To: Kar, Gouri X. -ND Cc: Kar, Gouri X. -ND; [EMAIL PROTECTED] Subject: RE: non-interactive ssh connections (was Re: RSYNC ISSUE) First, an item to fix: the substitution of -P for -p. All good operating systems are case-sensitive, and many utilities, ssh included, are case sensitive about their options. -P is passed along with the -p to signal that the next parameter is the passphrase, to enable passphrase setting directly in the commandline. If that's wrong, you're not touching the key at all. Secondly: Are you sure you're actually using the key? If the public key isn't in the authorized_keys file on the destination system, or if, for whatever other reason, the remote system won't use you key, you've got to solve that, first. It's common for people setting up ssh to make the passphrase the same as their login password. They test it, their password works, and they think they used the key, when in fact, they did password authentication. If, in fact, after setting the passphrase empty, you are able to ssh destination without providing a password, then we have something wierd going on. Tim Conway [EMAIL PROTECTED] 303.682.4917 office, 3039210301 cell 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? Kar, Gouri X. -ND [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/24/2002 11:52 AM To: Kar, Gouri X. -ND [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject:RE: non-interactive ssh connections (was Re: RSYNC ISSUE) Classification: Hi, I have tried to generate the key with ssh-keygen -P ( remove the passphrase) and copied it to the target system. However, it doesn't work. Any insite with the way I am distributing the KEYS -Original Message- From: Martin Pool [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 6:53 PM To: Kar, Gouri X. -ND Cc: [EMAIL PROTECTED]; Johnson, Gary X. -ND; Minyard, Mark X. -ND Subject: non-interactive ssh connections (was Re: RSYNC ISSUE) (Gouri: a more descriptive subject line will help you get repsonses in future, and please send your mail to [EMAIL PROTECTED] Read http://www.tuxedo.org/~esr/faqs/smart-questions.html) On 23 Jul 2002, Kar, Gouri X. -ND [EMAIL PROTECTED] wrote: Hi guys, I am trying to schdule a script which makes call to RSYNC over SSH. The same script works fine on the command prompt and sucessfully transfer the file from source to destination system with SSH. However, executing the script from CRONJOB doesn't work. It comes up with following error message From: daemon To: db2log You have no controlling tty and no DISPLAY. Cannot read passphrase. You have no controlling tty and no DISPLAY. Cannot read passphrase. warning: Authentication failed. Disconnected; authentication cancelled by
Re: superlifter design notes (was Re: Latest rZync release: 0.06)
2002-07-21-04:12:55 jw schultz: On Thu, Jul 11, 2002 at 07:06:29PM +1000, Martin Pool wrote: 6. No arbitrary limits: this is related to scalability. Filesizes and times should be 64-bit; names should be arbitrarily long. File sizes, yes. Times, no. unsigned 32 bit integers will last us for another 90 years. I suspect that by the time we need 64 bit timestamps the units will be milliseconds. I just don't see the need to waste an extra 4 bytes per timestamp per file. If bandwidth is of any interest at all, compress; any compression algorithm will have no trouble making hay with bulky, redundant timestamp formats. Rather than trying to optimize the protocol for bandwidth without compression, wouldn't it be better to try to optimize to future-proof in the face of changing time representations across systems? If I were designing a protocol at this level, I'd be using TAI; there's 64-bit time with 1 second resolution covering pretty much all time (more or less, depending on the whimsies of cosmologists:-); there are also longer variations with finer resolution. TAI, with appropriately fine resolution, should be able to represent any time that any other representation can, closer than anyone could care. TAI can be converted to other formats with more or less pain, depending on how demented the other formats are; djb's libtai is a reasonable starting point. URL:http://cr.yp.to/time.html has links to some pages discussing time formats. In short, though, Time since the epoch has a complication: leap-seconds. Either you end up having to move the epoch every time you bump into a leap-second, thereby redefining all times before that; or else you have duplicate times, where two different seconds have the same representation in seconds-since-the-epoch. Well, there's a third possibility, you could also let the current time drift further and further from what everybody else is using, but nobody seems to go for that one. -Bennett msg04673/pgp0.pgp Description: PGP signature
Problems compiling on RH 5.2.
Hello all, I recently downloaded RSYNC 2.5.5 and had a problem compiling on a RedHat 5.2 i386 system (I know its old but my co-located machine is ancient and I can't easily upgrade it). Anyhow, I did: ./configure --prefix=/usr/services/rsync And make fails because of the file lib/addrinfo.h not defining things correctly. The configure script generated: #define HAVE_GETADDRINFO 1 /* undef HAVE_GETADDRNAME */ Yet the way that works out I get undefined references to the NI_xxx constants in lib/addrinfo.h. They aren't in the standard headers for RH 5.2. So I tried disabling HAVE_GETADDRINFO and then compiling all that stuff since it looked like the RH 5.2 libraries had those functions but in an incompatible way. Then I got a ton of compile errors because stuff in lib/getaddrinfo.c conflicted with the standard headers. I managed to patch it together so it does work, including defining a number of symbols with alternate names at appropriate spots to fake out the compiler and linker. This probably needs to be fixed as the replacement approach to the C library doesn't work right. To probably compile somewhat portably, all of the #define's must be preceeded with #undef's and all of the symbols should include a prefix like rsync_ to avoid conflicts (including the structure tags). Thanks, Mark G. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
rsync hangs on w2k server running cygwin
Hi, I'm having trouble getting a clean run of rsync on a w2k server running cygwin. Basically, it appears that the commands are running to completion (i.e. files are being copied) but the command does not return to a command prompt (or continue to the next command when run via a script). The machine is a w2k server completely up-to-date with all service packs (SP2) and updates. I have just installed cygwin (1.3.12-2) and rsync (2.5.5-1) from the cygwin setup.exe program. The server has been rebooted and I have even tried re-installing the cygwin packages (and again rebooting) to make sure. At first I thought the hanging problem was due to using SSH but when I tried rsync simply copying local files (without SSH), I got the same behavior. I've searched google and the rsync mailing list and can't seem to find anything that addresses this issue. FWIW, I'm logged on to the w2k server with administrator's rights. Here is a log of the behavior: loki@SULTANA ~ $ rsync -vvr ~/test1/ ~/test2 building file list ... expand file_list to 4000 bytes, did move done hereisafile is uptodate total: matches=0 tag_hits=0 false_alarms=0 data=0 NOTE: from here it just hangs. The only way I can get the command prompt back is to ctrl-c. I have let it sit for many minutes without any luck. Also, as you can see from below, the directory and files are very small so it shouldn't take long. loki@SULTANA ~ $ ls -l total 2 drwxr-xr-x2 loki Domain U0 Jul 25 17:57 test1 drwxr-xr-x2 loki Domain U0 Jul 25 17:57 test2 loki@SULTANA ~ $ ls -l test1 total 1 -rw-r--r--1 loki Domain U 21 Jul 25 17:57 hereisafile loki@SULTANA ~ $ ls -l test2 total 1 -rw-r--r--1 loki Domain U 21 Jul 25 17:57 hereisafile Anyone have any ideas or have a similar problem? I'm happy to provide more information about the setup or command specifics. Thanks, Stirling -- 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 and open files
On 25 Jul 2002, Childs, Jim [EMAIL PROTECTED] wrote: Greetings. I have been looking around the web for information about what rsync does when the file being copied from is open and changing, but haven't seen this topic discussed anywhere. If you know of any place this is discussed, could you point me to it? Rsync looks like a great tool. We are still on the learning curve. The source file or the destination? If the source is changing, the results are undefined. Basically no other semantics are feasible on a machine without filesystem-level transactions. You will get some kind of mix of the various states, which is probably not what you want. If you're thinking of backing up, e.g., a database, you need to either shut it down, or take advantage of some kind of logging or rollover mechanism to make the relevant files quiescent. If the source file is merely being appended to, then I think you will be OK. The destination file is replaced by a new file when the transfer is complete, so anyone who has it open will keep writing to an unlinked file, and processes that open it afterwards will see the new file. -- 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
