As far as I know ssh doesn't send back return codes for scripts you execute remotely so your logic is a bit flawed there. Your test (if) is testing the ssh connection, I believe, so as long as you can ssh you'll test true. When you execute a command remotely with ssh you get back whatever is returned by the command so you need to execute a script on the remote server that looks for the file and returns what you want or just do it in a one-liner.
Code:
ssh user@remote 'if [ -f /home/batch/sample.txt ]; then echo "data file exists"; else echo "data file does not exist"; fi'
Hi All,
Thanks in Advance.
My requirement is there are some data files to be updated(some times new files get created) regularly in server A, these files are to be updated to the server B(backup server) by using SCP, I have to write a script for this purpose, before copying the files to server... (3 Replies)
Hello,
I used the search engine but could not find the solution I am looking for. Probably its simple but I do not know the solution.
My requirement is I ftp files every day in the morning from the remote server to the local machine. Now if the files are not there at the time I schedule the ftp... (2 Replies)
Hi
Does anybody know how I can check if a file exists
i.e. see bellow, this doesn't work by the way and if tried countless variations on this
file1=$one/file111.txt
if
then
echo "Present"
else
echo "Not present"
fi
result :
Not present
(file is already present, eventhough its... (3 Replies)
Hi,
I am trying to create a bash script which will check if file exist then remove that file else do nothing. I have to do same process for three files in same script. I have written code for one file and trying to run it.
if
then
rm -r /user1/abc/File1
fi
When I run this code it... (1 Reply)
Hi,
I created following script to check if file exist:
#!/bin/bash
SrcDir=$1
SrcFileName=$2
SrcTimePeriod=$3
if ;then
echo 1
else
echo 0
fi
I ran it like: /apps/Scripts/FileExist.sh /apps/Inbox file1 2nd_period_2010
Even file exist at that location, my above command is... (4 Replies)
Hi everyone,
I am trying to figure out a way to ssh to remote server and check if file exists, and if it doesn't I want to leave the script with an exit status of 5.
I have the following that I am attempting to use, but it is not returning anything:
check()
{
ssh ${SOURCE_SERV} "ls -l... (4 Replies)
Hi,
I need to check if a file exists on remote server using expect.
#!/bin/bash
ip_addr=10.10.10.10
user=root
passwd=Help
filename=/root/test
expect -c "
spawn ssh -n -T -o NumberOfPasswordPrompts=3 -o StrictHostKeyChecking=no $user@$ip_addr
expect \"*?assword:*\"
send --... (6 Replies)
Hi Experts,
I need a script in which I need to scp a file /home/chandan/abc.txt to a remote server using scp. Then I need to check whether scp is successful or not.
How am I going to write this code?
My Server Name: myserver
File Name On My Server: /home/chandan/abc.txt
Destination Server... (1 Reply)
Hi Experts,
I need a script in which I need to scp a file /home/chandan/abc.txt to a remote server using scp. Then I need to check whether scp is successful or not.
How am I going to write this code?
My Server Name: myserver
File Name On My Server: /home/chandan/abc.txt
Destination Server... (3 Replies)
Hi there,
I am sorry to ask that kind of beginner thing, but all the code I found online didnt work for me.
All I want to do is: Check via SSH if a File exists on my webserver. The SSH login has to be with username and password.
So I would be very thankful if somebody could write the line.... (8 Replies)
Discussion started by: Jens885544
8 Replies
LEARN ABOUT XFREE86
git-http-push
GIT-HTTP-PUSH(1) Git Manual GIT-HTTP-PUSH(1)NAME
git-http-push - Push objects over HTTP/DAV to another repository
SYNOPSIS
git http-push [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]
DESCRIPTION
Sends missing objects to remote repository, and updates the remote branch.
NOTE: This command is temporarily disabled if your libcurl is older than 7.16, as the combination has been reported not to work and
sometimes corrupts repository.
OPTIONS --all
Do not assume that the remote repository is complete in its current state, and verify all objects in the entire local ref's history
exist in the remote repository.
--force
Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it. This flag disables
the check. What this means is that the remote repository can lose commits; use it with care.
--dry-run
Do everything except actually send the updates.
--verbose
Report the list of objects being walked locally and the list of objects successfully sent to the remote repository.
-d, -D
Remove <ref> from remote repository. The specified branch cannot be the remote HEAD. If -d is specified the following other conditions
must also be met:
o Remote HEAD must resolve to an object that exists locally
o Specified branch resolves to an object that exists locally
o Specified branch is an ancestor of the remote HEAD
<ref>...
The remote refs to update.
SPECIFYING THE REFS
A <ref> specification can be either a single pattern, or a pair of such patterns separated by a colon ":" (this means that a ref name
cannot have a colon in it). A single pattern <name> is just a shorthand for <name>:<name>.
Each pattern pair consists of the source side (before the colon) and the destination side (after the colon). The ref to be pushed is
determined by finding a match that matches the source side, and where it is pushed is determined by using the destination side.
o It is an error if <src> does not match exactly one of the local refs.
o If <dst> does not match any remote ref, either
o it has to start with "refs/"; <dst> is used as the destination literally in this case.
o <src> == <dst> and the ref that matched the <src> must not exist in the set of remote refs; the ref matched <src> locally is used
as the name of the destination.
Without '--force`, the <src> ref is stored at the remote only if <dst> does not exist, or <dst> is a proper subset (i.e. an ancestor) of
<src>. This check, known as "fast-forward check", is performed in order to avoid accidentally overwriting the remote ref and lose other
peoples' commits from there.
With --force, the fast-forward check is disabled for all refs.
Optionally, a <ref> parameter can be prefixed with a plus + sign to disable the fast-forward check only on that ref.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-HTTP-PUSH(1)
07-14-2009
