10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi,
I am executing below command from Windows run and it is not working
"C:\Program Files (x86)\PuTTY\pageant.exe" "D:\abc_key.ppk" -c "C:\Program Files (x86)\PuTTY\plink.exe" -ssh 172.19.11.134 sh ~/touchfile.sh
I have created a .ppk file in the directory specified
The plink window... (2 Replies)
Discussion started by: NP1
2 Replies
2. Windows & DOS: Issues & Discussions
Hi,
I have run into a problem to which i can't seem to find any solution, posting here is my last resort.
Problem:
I am using plink to access my router and run a few configuration commands. When in enter configurations mode, instead of sending next command plink keeps on waiting for manual... (7 Replies)
Discussion started by: zaainabbas
7 Replies
3. Shell Programming and Scripting
I have similar issue as mentioned in
167174-how-run-script-using-batch-file.html
It works good, but the control is not coming back to source i tried adding exit to remote script.
Thanks,
Suresh (0 Replies)
Discussion started by: snsuresh
0 Replies
4. Shell Programming and Scripting
Hi All,
Iam a newbie to the plink and need your assistance. I have referred some posts but it doesn't helps me much.
I have two steps to do.
1. I have a config file which has a list of servers,username and password.
2. I have a shell script in windows which accepts arguments and need to... (0 Replies)
Discussion started by: cskumar
0 Replies
5. Shell Programming and Scripting
Hi Plink users,
I am very new in GWAS and decided to use PLINK for this. But I am struggling with file formats.
I have one exome data with 200000 SNPs in it. But it is in .txt format. But all the necessary fields are there in different columns.
Can you please suggest me how I can create the... (5 Replies)
Discussion started by: smitra
5 Replies
6. Shell Programming and Scripting
I'm using plink.exe on WinXP to run some commands on Z/OS BASH. My commands are interspersed with echo commands so that I can parse the output and work out what is where.
The first hundred or so commands run fine, but then one of them gets truncated. For example:
Input:
echo :end_logdetail:... (6 Replies)
Discussion started by: PhilHibbs
6 Replies
7. AIX
Hi,
I'm testing out this plink script - which will be executed to shutdown multiple LPARs.
This consists from:
plink -i /path/ssh/cert/ root@host shutdown -F
plink -i /path/ssh/cert/ root@host2 shutdown -F
The commands gets executed, however it stops on one host, and does not move... (6 Replies)
Discussion started by: ollie01
6 Replies
8. Shell Programming and Scripting
Im trying
C:\Program Files\PUTTY\plink.exe mysite.net -l username -pw mypassword -m restart.sh
But the login / password are never sent. If I remove the -m restart.sh it will login
I need the command inside restart.sh issued after the login password is completed.
THanks (6 Replies)
Discussion started by: Greystone
6 Replies
9. Shell Programming and Scripting
Hello. I have a TCL script that logs in to a server using SSH. As SSH isn't available in windows,I used Plink to do the job.The script works fine on my PC and 2 of my friend's PC.
However, on one PC, I get the following error message:
"'D:\scripts\plink.exe' is not a Win32 Console... (1 Reply)
Discussion started by: plasmalightwave
1 Replies
10. Shell Programming and Scripting
This is my shell script... test.sh
DIRECTORY=/XYZ/PQR
if ; then
echo "In test.."
else
echo "lno.."
fi
when i run this script through a putty its output is:
./test.sh: line 2: [: too many arguments
lno..
But when i run the same script using plink its running fine and its... (5 Replies)
Discussion started by: praveen.1
5 Replies
GIT-CAT-FILE(1) Git Manual GIT-CAT-FILE(1)
NAME
git-cat-file - Provide content or type and size information for repository objects
SYNOPSIS
git cat-file (-t [--allow-unknown-type]| -s [--allow-unknown-type]| -e | -p | <type> | --textconv | --filters ) [--path=<path>] <object>
git cat-file (--batch | --batch-check) [ --textconv | --filters ] [--follow-symlinks]
DESCRIPTION
In its first form, the command provides the content or the type of an object in the repository. The type is required unless -t or -p is
used to find the object type, or -s is used to find the object size, or --textconv or --filters is used (which imply type "blob").
In the second form, a list of objects (separated by linefeeds) is provided on stdin, and the SHA-1, type, and size of each object is
printed on stdout. The output format can be overridden using the optional <format> argument. If either --textconv or --filters was
specified, the input is expected to list the object names followed by the path name, separated by a single white space, so that the
appropriate drivers can be determined.
OPTIONS
<object>
The name of the object to show. For a more complete list of ways to spell object names, see the "SPECIFYING REVISIONS" section in
gitrevisions(7).
-t
Instead of the content, show the object type identified by <object>.
-s
Instead of the content, show the object size identified by <object>.
-e
Exit with zero status if <object> exists and is a valid object. If <object> is of an invalid format exit with non-zero and emits an
error on stderr.
-p
Pretty-print the contents of <object> based on its type.
<type>
Typically this matches the real type of <object> but asking for a type that can trivially be dereferenced from the given <object> is
also permitted. An example is to ask for a "tree" with <object> being a commit object that contains it, or to ask for a "blob" with
<object> being a tag object that points at it.
--textconv
Show the content as transformed by a textconv filter. In this case, <object> has to be of the form <tree-ish>:<path>, or :<path> in
order to apply the filter to the content recorded in the index at <path>.
--filters
Show the content as converted by the filters configured in the current working tree for the given <path> (i.e. smudge filters,
end-of-line conversion, etc). In this case, <object> has to be of the form <tree-ish>:<path>, or :<path>.
--path=<path>
For use with --textconv or --filters, to allow specifying an object name and a path separately, e.g. when it is difficult to figure out
the revision from which the blob came.
--batch, --batch=<format>
Print object information and contents for each object provided on stdin. May not be combined with any other options or arguments except
--textconv or --filters, in which case the input lines also need to specify the path, separated by white space. See the section BATCH
OUTPUT below for details.
--batch-check, --batch-check=<format>
Print object information for each object provided on stdin. May not be combined with any other options or arguments except --textconv
or --filters, in which case the input lines also need to specify the path, separated by white space. See the section BATCH OUTPUT below
for details.
--batch-all-objects
Instead of reading a list of objects on stdin, perform the requested batch operation on all objects in the repository and any alternate
object stores (not just reachable objects). Requires --batch or --batch-check be specified. Note that the objects are visited in order
sorted by their hashes.
--buffer
Normally batch output is flushed after each object is output, so that a process can interactively read and write from cat-file. With
this option, the output uses normal stdio buffering; this is much more efficient when invoking --batch-check on a large number of
objects.
--allow-unknown-type
Allow -s or -t to query broken/corrupt objects of unknown type.
--follow-symlinks
With --batch or --batch-check, follow symlinks inside the repository when requesting objects with extended SHA-1 expressions of the
form tree-ish:path-in-tree. Instead of providing output about the link itself, provide output about the linked-to object. If a symlink
points outside the tree-ish (e.g. a link to /foo or a root-level link to ../foo), the portion of the link which is outside the tree
will be printed.
This option does not (currently) work correctly when an object in the index is specified (e.g. :link instead of HEAD:link) rather than
one in the tree.
This option cannot (currently) be used unless --batch or --batch-check is used.
For example, consider a git repository containing:
f: a file containing "hello
"
link: a symlink to f
dir/link: a symlink to ../f
plink: a symlink to ../f
alink: a symlink to /etc/passwd
For a regular file f, echo HEAD:f | git cat-file --batch would print
ce013625030ba8dba906f756967f9e9ca394464a blob 6
And echo HEAD:link | git cat-file --batch --follow-symlinks would print the same thing, as would HEAD:dir/link, as they both point at
HEAD:f.
Without --follow-symlinks, these would print data about the symlink itself. In the case of HEAD:link, you would see
4d1ae35ba2c8ec712fa2a379db44ad639ca277bd blob 1
Both plink and alink point outside the tree, so they would respectively print:
symlink 4
../f
symlink 11
/etc/passwd
OUTPUT
If -t is specified, one of the <type>.
If -s is specified, the size of the <object> in bytes.
If -e is specified, no output, unless the <object> is malformed.
If -p is specified, the contents of <object> are pretty-printed.
If <type> is specified, the raw (though uncompressed) contents of the <object> will be returned.
BATCH OUTPUT
If --batch or --batch-check is given, cat-file will read objects from stdin, one per line, and print information about them. By default,
the whole line is considered as an object, as if it were fed to git-rev-parse(1).
You can specify the information shown for each object by using a custom <format>. The <format> is copied literally to stdout for each
object, with placeholders of the form %(atom) expanded, followed by a newline. The available atoms are:
objectname
The 40-hex object name of the object.
objecttype
The type of the object (the same as cat-file -t reports).
objectsize
The size, in bytes, of the object (the same as cat-file -s reports).
objectsize:disk
The size, in bytes, that the object takes up on disk. See the note about on-disk sizes in the CAVEATS section below.
deltabase
If the object is stored as a delta on-disk, this expands to the 40-hex sha1 of the delta base object. Otherwise, expands to the null
sha1 (40 zeroes). See CAVEATS below.
rest
If this atom is used in the output string, input lines are split at the first whitespace boundary. All characters before that
whitespace are considered to be the object name; characters after that first run of whitespace (i.e., the "rest" of the line) are
output in place of the %(rest) atom.
If no format is specified, the default format is %(objectname) %(objecttype) %(objectsize).
If --batch is specified, the object information is followed by the object contents (consisting of %(objectsize) bytes), followed by a
newline.
For example, --batch without a custom format would produce:
<sha1> SP <type> SP <size> LF
<contents> LF
Whereas --batch-check='%(objectname) %(objecttype)' would produce:
<sha1> SP <type> LF
If a name is specified on stdin that cannot be resolved to an object in the repository, then cat-file will ignore any custom format and
print:
<object> SP missing LF
If --follow-symlinks is used, and a symlink in the repository points outside the repository, then cat-file will ignore any custom format
and print:
symlink SP <size> LF
<symlink> LF
The symlink will either be absolute (beginning with a /), or relative to the tree root. For instance, if dir/link points to ../../foo, then
<symlink> will be ../foo. <size> is the size of the symlink in bytes.
If --follow-symlinks is used, the following error messages will be displayed:
<object> SP missing LF
is printed when the initial symlink requested does not exist.
dangling SP <size> LF
<object> LF
is printed when the initial symlink exists, but something that it (transitive-of) points to does not.
loop SP <size> LF
<object> LF
is printed for symlink loops (or any symlinks that require more than 40 link resolutions to resolve).
notdir SP <size> LF
<object> LF
is printed when, during symlink resolution, a file is used as a directory name.
CAVEATS
Note that the sizes of objects on disk are reported accurately, but care should be taken in drawing conclusions about which refs or objects
are responsible for disk usage. The size of a packed non-delta object may be much larger than the size of objects which delta against it,
but the choice of which object is the base and which is the delta is arbitrary and is subject to change during a repack.
Note also that multiple copies of an object may be present in the object database; in this case, it is undefined which copy's size or delta
base will be reported.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-CAT-FILE(1)