Hi,
I am facing a weired problem in my FTP script. I want to transfer multiple files from remote server to local server everyday, using mget * in my script. I also, want to send an email for successful or failed FTP. My script works for file transfer, but it don't send any mail. There is... (2 Replies)
Hi Friends,
Could you please help me as per my requirement mentioned below ?
I have to copy files from one unix server to another unix server, and the files that i need to copy from the remote server are only those which are modified/created Today from abc directory on the remote server (1 Reply)
We would be migrating unix solaries to Linux redhat.
Basically source is unix and target is linux.
i would like to copy entire file system unix/source/* to target linux/souce/*
but target linux has only folder setup so what ever files copied need to be placed in the linux server with same... (8 Replies)
I need to pull down a good bit of files for another support team for an upgrade project. I have a server.list with all of the server names.
I need to do two parts:
FIRST:
I have this example, but it does not list the server name in front of each line.
#! /bin/bash
for server in $(<... (10 Replies)
Hi there,
I have a problem in my script,
I need to check whether file exists in remote server or not,
if the file exists, then stop copy
else copy the file to the server..
my code is something like this
while read $server
do
if ssh $server "cd $directory_name; if ; then echo "Error:... (2 Replies)
Hi experts,
I 'm newbie to unix world, now I have task to copy the latest files from remote server to my local. I believe this must be very common request in this community. I want you do it one more time for me please.
My requirement is something like this:
I receive files in the below... (3 Replies)
Hi,
I am trying to automate the process of fetching files from remote server to local server through sftp. I have the username and password for the remote solaris server. But I need to give password manually everytime i run the script.
Can anyone help me in automating the script such that it... (3 Replies)
Hi All
I need to transfer a file from a UNIX server to a windows server.
I saw that it is possible to do this using scp command by looking at the forum listed below:
... (2 Replies)
I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
Discussion started by: digioleg54
3 Replies
LEARN ABOUT MOJAVE
mailaddr
MAILADDR(7) BSD Miscellaneous Information Manual MAILADDR(7)NAME
mailaddr -- mail addressing description
DESCRIPTION
Mail addresses are based on the Internet protocol listed at the end of this manual page. These addresses are in the general format
user@domain
where a domain is a hierarchical dot separated list of subdomains. For example, a valid address is:
eric@CS.Berkeley.EDU
Unlike some other forms of addressing, domains do not imply any routing. Thus, although this address is specified as an Internet address, it
might travel by an alternate route if that were more convenient or efficient. For example, at Berkeley, the associated message would proba-
bly go directly to CS over the Ethernet rather than going via the Berkeley Internet gateway.
Abbreviation.
Under certain circumstances it may not be necessary to type the entire domain name. In general, anything following the first dot may be
omitted if it is the same as the domain from which you are sending the message. For example, a user on ``calder.berkeley.edu'' could send to
``eric@CS'' without adding the ``berkeley.edu'' since it is the same on both sending and receiving hosts.
Compatibility.
Certain old address formats are converted to the new format to provide compatibility with the previous mail system. In particular,
user@host
and
user@host.domain
are allowed;
host.domain!user
is converted to
user@host.domain
and
host!user
is converted to
user@host.UUCP
This is normally converted back to the ``host!user'' form before being sent on for compatibility with older UUCP hosts.
Case Distinctions.
Domain names (i.e., anything after the ``@'' sign) may be given in any mixture of upper and lower case with the exception of UUCP hostnames.
Most hosts accept any combination of case in user names, with the notable exception of MULTICS sites.
Route-addrs.
Under some circumstances it may be necessary to route a message through several hosts to get it to the final destination. Normally this
routing is done automatically, but sometimes it is desirable to route the message manually. Addresses which show these relays are termed
``route-addrs.'' These use the syntax:
<@hosta,@hostb:user@hostc>
This specifies that the message should be sent to hosta, from there to hostb, and finally to hostc. This path is forced even if there is a
more efficient path to hostc.
Route-addrs occur frequently on return addresses, since these are generally augmented by the software at each host. It is generally possible
to ignore all but the ``user@hostc'' part of the address to determine the actual sender.
[Note: the route-addr syntax is officially deprecated in RFC 1123 and should not be used.]
Many sites also support the ``percent hack'' for simplistic routing:
user%hostc%hostb@hosta
is routed as indicated in the previous example.
Postmaster.
Every site is required to have a user or user alias designated ``postmaster'' to which problems with the mail system may be addressed.
Other Networks.
Some other networks can be reached by giving the name of the network as the last component of the domain. This is not a standard feature and
may not be supported at all sites. For example, messages to CSNET or BITNET sites can often be sent to ``user@host.CSNET'' or
``user@host.BITNET'' respectively.
SEE ALSO mail(1), sendmail(8)
Crocker, D. H., Standard for the Format of Arpa Internet Text Messages, RFC822.
HISTORY
Mailaddr appeared in 4.2BSD.
BUGS
The RFC822 group syntax (``group:user1,user2,user3;'') is not supported except in the special case of ``group:;'' because of a conflict with
old berknet-style addresses.
Route-Address syntax is grotty.
UUCP- and Internet-style addresses do not coexist politely.
BSD June 16, 1993 BSD