Dear Friend,
I don't know much about unix.I am an VB6.0 Programmer.I need to move an text files as aaa.txt from unix server to windows "D: " driver using the FTP protocol.Is it possible to do this with help of unix shell script.If possible please give some sample codes.
Please answer as early... (1 Reply)
I want to transfer files from the server 1 to server 2, but only information available FTP my server 2
How?
Is there a script help me in the transfer of files through FTP :( (2 Replies)
I need to write a shell script to transfer the files every hour from source - target server.
The cron job should be running every hour and shouldn't copy already copied files to the remote server ?
I was able to write intial script but not able to get the logic for (in the next run it should... (12 Replies)
Hello Unix Gurus,
Help required from you.
My requirement is something like this
I want to create a concurrenct program in Oracle Applications using shell script to transfer files from Apps Server to destination FTP server.
I have created custom program, where I will extract all the... (4 Replies)
Hello,
i have to write a script to perform sftp from the remote server to another server.
the files which are at the remote location are huge data log files which should be transfered to my server in a particular folder.
could you please provide me the general code (simple )... (1 Reply)
I have 3 servers A, B, C and server B is having some files in /u01/soa/ directory, these files i want to copy to server C, and i want to run the script from server A.
Script(Server A) --> Files at Server B (Source server) --> Copy the files to Server C(Target Server).
We dont have RSA key... (4 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)
Hello to all,
I want to copy from one server to another files of last 24 hours with size between 500MB and 2GB. The code below searches last files in 24 hours.
find . -mtime -1
In order to copy faster I'd like to compress the files before copying them.
How to automate the process of... (8 Replies)
Hi Guyz ,,
I'm an ERP functional guy , I really need to automate a script which required a shell script but have a little knowledge in shell scripting.
I need my generated files to be zipped first in one directory lets say (xyz) and then it needs to transfer another ftp server in... (3 Replies)
Hi All,
I have generated public and private pair to avoid to enter password manually while sending files through sftp.
But still I am facing issues and every-time prompt asking enter password.
Below are steps I fallowed to make ssh connection between two servers.
1. Generated public and... (5 Replies)
Discussion started by: renukeswar
5 Replies
LEARN ABOUT CENTOS
git-check-ref-format
GIT-CHECK-REF-FOR(1) Git Manual GIT-CHECK-REF-FOR(1)NAME
git-check-ref-format - Ensures that a reference name is well formed
SYNOPSIS
git check-ref-format [--normalize]
[--[no-]allow-onelevel] [--refspec-pattern]
<refname>
git check-ref-format --branch <branchname-shorthand>
DESCRIPTION
Checks if a given refname is acceptable, and exits with a non-zero status if it is not.
A reference is used in Git to specify branches and tags. A branch head is stored in the refs/heads hierarchy, while a tag is stored in the
refs/tags hierarchy of the ref namespace (typically in $GIT_DIR/refs/heads and $GIT_DIR/refs/tags directories or, as entries in file
$GIT_DIR/packed-refs if refs are packed by git gc).
Git imposes the following rules on how references are named:
1. They can include slash / for hierarchical (directory) grouping, but no slash-separated component can begin with a dot . or end with
the sequence .lock.
2. They must contain at least one /. This enforces the presence of a category like heads/, tags/ etc. but the actual names are not
restricted. If the --allow-onelevel option is used, this rule is waived.
3. They cannot have two consecutive dots .. anywhere.
4. They cannot have ASCII control characters (i.e. bytes whose values are lower than 40, or 177 DEL), space, tilde ~, caret ^, or colon
: anywhere.
5. They cannot have question-mark ?, asterisk *, or open bracket [ anywhere. See the --refspec-pattern option below for an exception to
this rule.
6. They cannot begin or end with a slash / or contain multiple consecutive slashes (see the --normalize option below for an exception to
this rule)
7. They cannot end with a dot ..
8. They cannot contain a sequence @{.
9. They cannot contain a .
These rules make it easy for shell script based tools to parse reference names, pathname expansion by the shell when a reference name is
used unquoted (by mistake), and also avoids ambiguities in certain reference name expressions (see gitrevisions(7)):
1. A double-dot .. is often used as in ref1..ref2, and in some contexts this notation means ^ref1 ref2 (i.e. not in ref1 and in ref2).
2. A tilde ~ and caret ^ are used to introduce the postfix nth parent and peel onion operation.
3. A colon : is used as in srcref:dstref to mean "use srcref's value and store it in dstref" in fetch and push operations. It may also be
used to select a specific object such as with git cat-file: "git cat-file blob v1.3.3:refs.c".
4. at-open-brace @{ is used as a notation to access a reflog entry.
With the --branch option, it expands the "previous branch syntax" @{-n}. For example, @{-1} is a way to refer the last branch you were on.
This option should be used by porcelains to accept this syntax anywhere a branch name is expected, so they can act as if you typed the
branch name.
OPTIONS
--[no-]allow-onelevel
Controls whether one-level refnames are accepted (i.e., refnames that do not contain multiple /-separated components). The default is
--no-allow-onelevel.
--refspec-pattern
Interpret <refname> as a reference name pattern for a refspec (as used with remote repositories). If this option is enabled, <refname>
is allowed to contain a single * in place of a one full pathname component (e.g., foo/*/bar but not foo/bar*).
--normalize
Normalize refname by removing any leading slash (/) characters and collapsing runs of adjacent slashes between name components into a
single slash. Iff the normalized refname is valid then print it to standard output and exit with a status of 0. (--print is a
deprecated way to spell --normalize.)
EXAMPLES
o Print the name of the previous branch:
$ git check-ref-format --branch @{-1}
o Determine the reference name to use for a new branch:
$ ref=$(git check-ref-format --normalize "refs/heads/$newbranch") ||
die "we do not like '$newbranch' as a branch name."
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-CHECK-REF-FOR(1)