Sponsored Content
Full Discussion: recursive rcp
Top Forums Shell Programming and Scripting recursive rcp Post 42896 by Nicol on Thursday 6th of November 2003 10:52:10 AM
Old 11-06-2003
in french , we say "bon dieu mais c'est bien sûr"

=> oh god for sure

sorry i'm surely tired , it was so simple !

thanks a lot

christian
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rcp in SCO 5.0.7

I am installing 5.0.7 on an existing SCO network. The 2 other machines are using 5.0.5 and rcp works daily both ways between the 2 older machines. However I cannot copy from either machine running 5.0.5 to the new 5.0.7 machine - "Permission Denied" /etc/hosts is configured correctly... (4 Replies)
Discussion started by: farmacy
4 Replies

2. UNIX for Advanced & Expert Users

rcp error

I'm trying to perform a rcp to a remote machine, but it keeps throwing up "LOGNAME: undefined variable" error. When I echo $LOGNAME, it comes up with my username. I have tried setting both the .rhosts and the .hosts.equiv file but to no avail (on both machines as well out of desperation!). Anyone... (8 Replies)
Discussion started by: divid_gil
8 Replies

3. HP-UX

rcp logs

Hi, Can anyone help me to trace who has made rcp to a HP-UX machine? Is there a file that keeps such records? I know ftp's are recorded in /var/adm/syslog but i only need rcp.Thanks... (0 Replies)
Discussion started by: ilkergu
0 Replies

4. UNIX for Dummies Questions & Answers

Rcp

I am trying to set up RCP so root can access a few machines for file transfer. On the target machine, I have set up a .RHOSTS file that looks like: 10.33.1.59 root However when I try to use RCP to copy a file to this machine, I get permission denied. Is it possible since another user is... (1 Reply)
Discussion started by: hshapiro
1 Replies

5. UNIX for Dummies Questions & Answers

help on rcp,exportfs

i need some help on remote file copyieng.the queeries are: 1:> m working on a machine say(abc) and i want to copy a directory(yes a directory) from a remote machine. so what would be the command. 2:> do in need to login on the source machine from where i want to copy a directory. 3:> is it... (0 Replies)
Discussion started by: mxms755
0 Replies

6. Shell Programming and Scripting

rcp the file

Hi I am using rcp command to copy the file one linux to other linux machine I need the ouput log for this like 1 file coied size of the file date stamp my copy comman is rcp 10.100.11.2:/u01/pr/uni.txt /u05/ryd/uni.txt once this script run i need to capture the... (3 Replies)
Discussion started by: aboorkuma
3 Replies

7. Shell Programming and Scripting

rcp problem

Hi, When I try to use rcp I donīt recieve the file I try to fetch. I donīt get any error message, it just execute and as far as I can tell doesnīt do anything. I have no problem with using remsh to list the directory. remsh 132.196.133.185 -l root ls xdpyinfo: unable to open display... (7 Replies)
Discussion started by: mr_andrew
7 Replies

8. UNIX for Dummies Questions & Answers

RCP command

hi, When i use RCP command to copy filr from a different servers, it is showing as connection refused??? ca anyone help me out??? thanks, Arun Manas:b: (2 Replies)
Discussion started by: arunmanas
2 Replies

9. Shell Programming and Scripting

rcp -r || cp -r

what different between two instruction cp -r rcp -r (1 Reply)
Discussion started by: tamer11007
1 Replies

10. Solaris

Rcp between 2 computers

Hi, I need to rcp heavy files between 2 solaris 10/sparc M3000 computers. Currently theses 2 computers are linked via a switch/firewall and the rcp commands take a very long time, I have been told that this is because of the firewall (old one). I asked my client to by a cross ethernet cable and... (2 Replies)
Discussion started by: zionassedo
2 Replies
envelopes(5)                                                    File Formats Manual                                                   envelopes(5)

NAME
envelopes - sender/recipient lists attached to messages INTRODUCTION
Electronic mail messages are delivered in envelopes. An envelope lists a sender and one or more recipients. Usually these envelope addresses are the same as the addresses listed in the mes- sage header: (envelope) from djb to root From: djb To: root In more complicated situations, though, the envelope addresses may differ from the header addresses. ENVELOPE EXAMPLES
When a message is delivered to several people at different locations, it is first photocopied and placed into several envelopes: (envelope) from djb to root From: djb Copy #1 of message To: root, god@brl.mil (envelope) from djb to god@brl.mil From: djb Copy #2 of message To: root, god@brl.mil When a message is delivered to several people at the same location, the sender doesn't have to photocopy it. He can instead stuff it into one envelope with several addresses; the recipients will make the photocopy: (envelope) from djb to god@brl.mil, angel@brl.mil From: djb To: god@brl.mil, angel@brl.mil, joe, frde Bounced mail is sent back to the envelope sender address. The bounced mail doesn't list an envelope sender, so bounce loops are impossi- ble: (envelope) from <> to djb From: MAILER-DAEMON To: djb Subject: unknown user frde The recipient of a message may make another copy and forward it in a new envelope: (envelope) from djb to joe From: djb Original message To: joe (envelope) from joe to fred From: djb Forwarded message To: joe A mailing list works almost the same way: (envelope) from djb to sos-list From: djb Original message To: sos-list (envelope) from sos-owner to god@brl.mil From: djb Forwarded message To: sos-list to recipient #1 (envelope) from sos-owner to frde From: djb Forwarded message To: sos-list to recipient #2 Notice that the mailing list is set up to replace the envelope sender with something new, sos-owner. So bounces will come back to sos- owner: (envelope) from <> to sos-owner From: MAILER-DAEMON To: sos-owner Subject: unknown user frde It's a good idea to set up an extra address, sos-owner, like this: the original envelope sender (djb) has no way to fix bad sos-list addresses, and of course bounces must not be sent to sos-list itself. HOW ENVELOPE ADDRESSES ARE STORED
Envelope sender and envelope recipient addresses are transmitted and recorded in several ways. When a user injects mail through qmail-inject, he can supply a Return-Path line or a -f option for the envelope sender; by default the envelope sender is his login name. The envelope recipient addresses can be taken from the command line or from various header fields, depending on the options to qmail-inject. Similar comments apply to sendmail. When a message is transferred from one machine to another through SMTP, the envelope sender is given in a MAIL FROM command, the envelope recipients are given in RCPT TO commands, and the message is supplied separately by a DATA command. When a message is delivered by qmail to a single local recipient, qmail-local records the recipient in Delivered-To and the envelope sender in Return-Path. It uses Delivered-To to detect mail forwarding loops. sendmail normally records the envelope sender in Return-Path. It does not record envelope recipient addresses, on the theory that they are redundant: you received the mail, so you must have been one of the envelope recipients. Note that, if the header doesn't have any recipient addresses, sendmail will move envelope recipient addresses back into the header. This situation occurs if all addresses were originally listed as Bcc, since Bcc is automatically removed. When sendmail sees this, it creates a new Apparently-To header field with the envelope recipient addresses. This has the strange effect that each blind-carbon-copy recipient will see a list of all recipients on the same machine. When a message is stored in mbox format, the envelope sender is recorded at the top of the message as a UUCP-style From (no colon) line. Note that this line is less reliable than the Return-Path line added by qmail-local or sendmail. SEE ALSO
qmail-header(5), qmail-local(8), qmail-inject(8) envelopes(5)
All times are GMT -4. The time now is 06:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy