I have to ftp and rename the file with #finished# extension after successfully transfer. In some environments the command
is working fine, but some environments its not working, I have to use escape character something like :
Why is it behaving differently? Both servers are running on Linux same version and korn shell.
I doin a script in sh.
For example:
i have this code here whereby $5 is a text file. eg file.txt. I wanna rename it to file.txt.tmp. so i use this code below which is correct.
put $5 $5.tmp
But when the ftp transfer is complete i need to rename the file back to $5 which is file.txt.
How do... (2 Replies)
hi friends,
I writing a script to psot dataset to ceratin server.....while doing ftp I have to rename the file while which is in present server like
present :test server
filename data.097878.
ftp server: it sholu be renamed as data.097878.zip
thanks,
The thing is that while... (1 Reply)
Hi All,
I want to rename set of files in the remote server which iam unable to do . i can rename only one file
at a time . for example
ftp $REMOTESERVER
{
rename $NAME1 $NAME2
} is working
whereas
ftp $REMOTESERVER
{
rename $NAME1*.dat $NAME2*.data
} is not working ...... (4 Replies)
Hi
I have following list of files at a path:
01.AR.asset
01.AR.index
01.AR.asset.vf
01.AR.asset.xv
I want to rename all these files as follows:
73.AR.asset.Z
73.AR.index.Z
73.AR.asset.vf.Z
73.AR.asset.xv.Z
Can any body give me a single command to acheive the above results.
... (5 Replies)
How do i rename all the files using a script ?
My server create log files and save them with numbering behind the name. for e.g. daily_20080101.log.0001 and so on ... How do a script and crontab it to remove all the numbering? Please help thanks. (2 Replies)
Greetings,
I am very new to the UNIX shell scripting and would like to learn. However, I am currently stuck on how to process the below sample :
Filename : DOCabcdef24387987ab90d.xml
Pattern "DOC"+any character using and +".xml"
And i want to change the second part of that file (any... (20 Replies)
Hi all,
I wish to know about a simple concept of mv command in UNIX. Is moving a file to a different directory takes longer than renaming it in the same direcotry using the mv command?
The scenerio is that I have to transfer a file from one directory to a location which is regularly scanned... (3 Replies)
Hello All,
I am trying to connect to ftp server and get the files. Also i need to rename the file in other ftp dir.
rename method is not allowing me to rename the file in other dir. When i tried copy command by using net::FTP:FILE then perl says it is not installed.
Can some body help me to... (2 Replies)
Hi,
I have a large series of directories and subdirectories with many jpgs in them. I need to do two things:
1. Create a copy of each jpg found within it's own subdirectory
2. Rename this copied jpg such that apple.jpg becomes apple_m.jpg
I have tried to run the following commands in... (1 Reply)
Hey all, I really need help with some homework I'm having on UNIX. This probably sounds stupid, but I'm being asked to move a file to a specific directory and rename it a specified name in one command. I know how to do it in more than one command, I just can't seem to figure it out using only one... (1 Reply)
Discussion started by: ayylmao12
1 Replies
LEARN ABOUT CENTOS
gitnamespaces
GITNAMESPACES(7) Git Manual GITNAMESPACES(7)NAME
gitnamespaces - Git namespaces
SYNOPSIS
GIT_NAMESPACE=<namespace> git upload-pack
GIT_NAMESPACE=<namespace> git receive-pack
DESCRIPTION
Git supports dividing the refs of a single repository into multiple namespaces, each of which has its own branches, tags, and HEAD. Git can
expose each namespace as an independent repository to pull from and push to, while sharing the object store, and exposing all the refs to
operations such as git-gc(1).
Storing multiple repositories as namespaces of a single repository avoids storing duplicate copies of the same objects, such as when
storing multiple branches of the same source. The alternates mechanism provides similar support for avoiding duplicates, but alternates do
not prevent duplication between new objects added to the repositories without ongoing maintenance, while namespaces do.
To specify a namespace, set the GIT_NAMESPACE environment variable to the namespace. For each ref namespace, Git stores the corresponding
refs in a directory under refs/namespaces/. For example, GIT_NAMESPACE=foo will store refs under refs/namespaces/foo/. You can also specify
namespaces via the --namespace option to git(1).
Note that namespaces which include a / will expand to a hierarchy of namespaces; for example, GIT_NAMESPACE=foo/bar will store refs under
refs/namespaces/foo/refs/namespaces/bar/. This makes paths in GIT_NAMESPACE behave hierarchically, so that cloning with
GIT_NAMESPACE=foo/bar produces the same result as cloning with GIT_NAMESPACE=foo and cloning from that repo with GIT_NAMESPACE=bar. It also
avoids ambiguity with strange namespace paths such as foo/refs/heads/, which could otherwise generate directory/file conflicts within the
refs directory.
git-upload-pack(1) and git-receive-pack(1) rewrite the names of refs as specified by GIT_NAMESPACE. git-upload-pack and git-receive-pack
will ignore all references outside the specified namespace.
The smart HTTP server, git-http-backend(1), will pass GIT_NAMESPACE through to the backend programs; see git-http-backend(1) for sample
configuration to expose repository namespaces as repositories.
For a simple local test, you can use git-remote-ext(1):
git clone ext::'git --namespace=foo %s /tmp/prefixed.git'
SECURITY
Anyone with access to any namespace within a repository can potentially access objects from any other namespace stored in the same
repository. You can't directly say "give me object ABCD" if you don't have a ref to it, but you can do some other sneaky things like:
1. Claiming to push ABCD, at which point the server will optimize out the need for you to actually send it. Now you have a ref to ABCD and
can fetch it (claiming not to have it, of course).
2. Requesting other refs, claiming that you have ABCD, at which point the server may generate deltas against ABCD.
None of this causes a problem if you only host public repositories, or if everyone who may read one namespace may also read everything in
every other namespace (for instance, if everyone in an organization has read permission to every repository).
Git 1.8.3.1 06/10/2014 GITNAMESPACES(7)