I tried it two ways both resulting in file or directory not found, but I can manually ssh to them. This is not the full code but I hope it's enough as I don't want to post code that is not needed. Thank you .
attempt 1
attempt 2
attempt 1 error:
attempt 2 error: --- in the server these exsist as ID1-xxxx-xxxxxxx-xxxxxx so I added * but thats not expanding it seems ----
Last edited by cmccabe; 10-16-2019 at 01:40 PM..
Reason: fixed format
Hi,
I'm trying to write a function that redirects the contents of an
array to a file. The array contains the lines of a data file with
white space.
The function seems to preserve all white space when redirected
except that it seems to ignore newlines. As a consequence, the
elements of the... (7 Replies)
Hi Guys,
I have a file which has numbers in it separated by newlines as follows:
1.113
1.456
0.556
0.021
-0.541
-0.444
I am using the following code to store these in an array in bash:
FILE14=data.txt
ARRAY14=(`awk '{print}' $FILE14`) (6 Replies)
I have one file "file.a.b.c-d.r" that I would like to use to spawn 4 other files:
"file.a.b.1-A.r"
"file.a.b.1-B.r"
"file.a.b.1-C.r"
"file.a.b.1-D.r"
where the field "c-d" changes into my 1 and A-D.
I was doing this manually at the prompt with
> cp "file.a.b.c-d.r" "file.a.b.1-A.r"
>... (13 Replies)
I have figured out how to grep the file like this:
echo `grep $(date +'%Y-%m-%d') Cos-01.csv | cut -d',' -f1`
The above line does echo the correct information from the lines in which my search criteria is found.
Now I am trying to get that information (Yes, just one column of every line) into... (6 Replies)
Writing a bash script for use with Geektool, pulls the battery info, and shuffles images around so that an Image geeklet can display the correct expression as the desktop background. (Eventually I intend to make it more intricate, based on more variables, and add more expressions)
I'm extremely... (1 Reply)
Hi,
I'm trying to write a bash script that takes a file and passes each line from the file into an array with elements separated by column.
For example:
Sample file "file1.txt":
1 name1 a first
2 name2 b second
3 name3 c third
and have arrays such as:
line1 = ( "1" "name1" "a"... (3 Replies)
for a in {1..100}
do
awk '{ sum+=$a} END {print sum}' a=$a file1 > file2
done
I know I will get only one number if following the code above, how can I get 100 sum numbers in file2? (2 Replies)
I'm working on a bash script to finish uploading a file.
I need a way to get $filesize so that "restart $filesize" will work.
Here is my script:
ftp -n -v <<END_SCRIPT
open ftp.$domain
user $user@$domain $password
size $file
restart $filesize
put $file
quit
END_SCRIPTWayne Sallee... (9 Replies)
Hi Team,
i have a web ui where user will be passing values and the output will be saved to a file say test with the following contents .
These below mentioned values will change according to the user_input
Just gave here one example
Contents of file test is given below
Gateway... (7 Replies)
Hi guys and gals...
MacBook Pro.
OSX 10.13.2, default bash terminal.
I have a flat file 1920 bytes in size of whitespaces only. I need to put every single whitespace character into a bash array cell.
Below are two methods that work, but both are seriously ugly.
The first one requires that I... (7 Replies)
Discussion started by: wisecracker
7 Replies
LEARN ABOUT LINUX
git-receive-pack
GIT-RECEIVE-PACK(1) Git Manual GIT-RECEIVE-PACK(1)NAME
git-receive-pack - Receive what is pushed into the repository
SYNOPSIS
git-receive-pack <directory>
DESCRIPTION
Invoked by git send-pack and updates the repository with the information fed from the remote end.
This command is usually not invoked directly by the end user. The UI for the protocol is on the git send-pack side, and the program pair is
meant to be used to push updates to remote repository. For pull operations, see git-fetch-pack(1).
The command allows for creation and fast-forwarding of sha1 refs (heads/tags) on the remote end (strictly speaking, it is the local end
git-receive-pack runs, but to the user who is sitting at the send-pack end, it is updating the remote. Confused?)
There are other real-world examples of using update and post-update hooks found in the Documentation/howto directory.
git-receive-pack honours the receive.denyNonFastForwards config option, which tells it if updates to a ref should be denied if they are not
fast-forwards.
OPTIONS
<directory>
The repository to sync into.
PRE-RECEIVE HOOK
Before any ref is updated, if $GIT_DIR/hooks/pre-receive file exists and is executable, it will be invoked once with no parameters. The
standard input of the hook will be one line per ref to be updated:
sha1-old SP sha1-new SP refname LF
The refname value is relative to $GIT_DIR; e.g. for the master head this is "refs/heads/master". The two sha1 values before each refname
are the object names for the refname before and after the update. Refs to be created will have sha1-old equal to 0{40}, while refs to be
deleted will have sha1-new equal to 0{40}, otherwise sha1-old and sha1-new should be valid objects in the repository.
This hook is called before any refname is updated and before any fast-forward checks are performed.
If the pre-receive hook exits with a non-zero exit status no updates will be performed, and the update, post-receive and post-update hooks
will not be invoked either. This can be useful to quickly bail out if the update is not to be supported.
UPDATE HOOK
Before each ref is updated, if $GIT_DIR/hooks/update file exists and is executable, it is invoked once per ref, with three parameters:
$GIT_DIR/hooks/update refname sha1-old sha1-new
The refname parameter is relative to $GIT_DIR; e.g. for the master head this is "refs/heads/master". The two sha1 arguments are the object
names for the refname before and after the update. Note that the hook is called before the refname is updated, so either sha1-old is 0{40}
(meaning there is no such ref yet), or it should match what is recorded in refname.
The hook should exit with non-zero status if it wants to disallow updating the named ref. Otherwise it should exit with zero.
Successful execution (a zero exit status) of this hook does not ensure the ref will actually be updated, it is only a prerequisite. As such
it is not a good idea to send notices (e.g. email) from this hook. Consider using the post-receive hook instead.
POST-RECEIVE HOOK
After all refs were updated (or attempted to be updated), if any ref update was successful, and if $GIT_DIR/hooks/post-receive file exists
and is executable, it will be invoked once with no parameters. The standard input of the hook will be one line for each successfully
updated ref:
sha1-old SP sha1-new SP refname LF
The refname value is relative to $GIT_DIR; e.g. for the master head this is "refs/heads/master". The two sha1 values before each refname
are the object names for the refname before and after the update. Refs that were created will have sha1-old equal to 0{40}, while refs that
were deleted will have sha1-new equal to 0{40}, otherwise sha1-old and sha1-new should be valid objects in the repository.
Using this hook, it is easy to generate mails describing the updates to the repository. This example script sends one mail message per ref
listing the commits pushed to the repository:
#!/bin/sh
# mail out commit update information.
while read oval nval ref
do
if expr "$oval" : '0*$' >/dev/null
then
echo "Created a new ref, with the following commits:"
git rev-list --pretty "$nval"
else
echo "New commits:"
git rev-list --pretty "$nval" "^$oval"
fi |
mail -s "Changes to ref $ref" commit-list@mydomain
done
exit 0
The exit code from this hook invocation is ignored, however a non-zero exit code will generate an error message.
Note that it is possible for refname to not have sha1-new when this hook runs. This can easily occur if another user modifies the ref after
it was updated by git-receive-pack, but before the hook was able to evaluate it. It is recommended that hooks rely on sha1-new rather than
the current value of refname.
POST-UPDATE HOOK
After all other processing, if at least one ref was updated, and if $GIT_DIR/hooks/post-update file exists and is executable, then
post-update will be called with the list of refs that have been updated. This can be used to implement any repository wide cleanup tasks.
The exit code from this hook invocation is ignored; the only thing left for git-receive-pack to do at that point is to exit itself anyway.
This hook can be used, for example, to run git update-server-info if the repository is packed and is served via a dumb transport.
#!/bin/sh
exec git update-server-info
SEE ALSO git-send-pack(1), gitnamespaces(7)GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-RECEIVE-PACK(1)