10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
I need to join fixed width files on a column which is position 1 to 3 and need to have all the records from file1
file1.txt
Cu1nullL1L2
Cu2nullL1L2
Cu3nullL1L2
file2.txt
Cu1B1B2
Cu3B1B2
output.txt
Cu1L1B1L2B2
Cu2L1L2
Cu3L1B1L2B3
I tried but not getting the expected... (12 Replies)
Discussion started by: shash
12 Replies
2. Shell Programming and Scripting
Hi All ,
I have a requirement where I need to remove duplicates from a fixed width file which has multiple key columns .Also , need to capture the duplicate records into another file .
File has 8 columns.
Key columns are col1 and col2.
Col1 has the length of 8 col 2 has the length of 3.
... (5 Replies)
Discussion started by: saj
5 Replies
3. UNIX for Advanced & Expert Users
actually i am trying to find the lenght of fixed width file record reading from teradata db but its not working can u guys help me out?
code which i wrote---
colmn_lngth=`cat $RPT_FILE | awk -F~ '{print $1}'`
rm $RPT_FILE
while read line
do
result=`echo $line | wc -m`
... (4 Replies)
Discussion started by: Seshendranath
4 Replies
4. Shell Programming and Scripting
Hi there,
CTL Port IO Rate(IOPS) Read Rate(IOPS) Write Rate(IOPS) Read Hit(%) Write Hit(%) Trans. Rate(MB/S) Read Trans. Rate(MB/S) Write Trans. Rate(MB/S) 09:36:48
0 A 136 0 135 97 100 ... (6 Replies)
Discussion started by: gray380
6 Replies
5. Shell Programming and Scripting
Hi Guys
I am checking the treads to get the answer but i am not able to get the answer for my question.
I have two files. First file is a pattern file and the second file is the file i want to search in it. Output will be the lines from file2.
File1:
P2797f12af 44751228... (10 Replies)
Discussion started by: anshul_er
10 Replies
6. Shell Programming and Scripting
Hi All,
I have created a script which generates FIXED-WIDTH file by executing Oracle query.
SELECT RPAD(NVL(col1,CHR(9)),20)||NVL(col2,CHR(9))||NVL(col3,CHR(9) FROM XYZ
It generates the data file with proper alignment. But if same file i transfer to windows server or Mainframe... (5 Replies)
Discussion started by: Amit.Sagpariya
5 Replies
7. Shell Programming and Scripting
Hi everyone,
I have been working on a pretty laborious shellscript (with bash) the last couple weeks that parses my firewall policies (from a Juniper) for me and creates a nifty little columned output. It does so using awk on a line by line basis to pull out the appropriate pieces of each... (4 Replies)
Discussion started by: cixelsyd
4 Replies
8. Shell Programming and Scripting
Hi champs!
I have a fixed width file in which the records appear like this
11111 <fixed spaces such as 6> description for 11111 <fixed spaces such as 6> some more field to the record of 11111
22222 <fixed spaces such as 6> description for 22222 <fixed spaces such as 6> some more field to the... (8 Replies)
Discussion started by: enigma_1
8 Replies
9. UNIX Desktop Questions & Answers
I am trying to parse a Fixed width file with data as below. I am trying to assign column values from each record to variables. When I parse the data, the spaces in all coumns are dropped. I would like to retain the spaces as part of the dat stored in the variables. Any help is appreciated.
I... (4 Replies)
Discussion started by: sate911
4 Replies
10. Shell Programming and Scripting
I have a fixed width flatfile with 5 columns, i will load file from oracle database to the flatfile for every 15 min at the end of the file, i want to insert a record by calling a shell script for inserting a record.
please can any one help me.
Thanks. (1 Reply)
Discussion started by: limou
1 Replies
GIT-RM(1) Git Manual GIT-RM(1)
NAME
git-rm - Remove files from the working tree and from the index
SYNOPSIS
git rm [-f | --force] [-n] [-r] [--cached] [--ignore-unmatch] [--quiet] [--] <file>...
DESCRIPTION
Remove files from the index, or from the working tree and the index. git rm will not remove a file from just your working directory. (There
is no option to remove a file only from the working tree and yet keep it in the index; use /bin/rm if you want to do that.) The files being
removed have to be identical to the tip of the branch, and no updates to their contents can be staged in the index, though that default
behavior can be overridden with the -f option. When --cached is given, the staged content has to match either the tip of the branch or the
file on disk, allowing the file to be removed from just the index.
OPTIONS
<file>...
Files to remove. Fileglobs (e.g. *.c) can be given to remove all matching files. If you want Git to expand file glob characters, you
may need to shell-escape them. A leading directory name (e.g. dir to remove dir/file1 and dir/file2) can be given to remove all files
in the directory, and recursively all sub-directories, but this requires the -r option to be explicitly given.
-f, --force
Override the up-to-date check.
-n, --dry-run
Don't actually remove any file(s). Instead, just show if they exist in the index and would otherwise be removed by the command.
-r
Allow recursive removal when a leading directory name is given.
--
This option can be used to separate command-line options from the list of files, (useful when filenames might be mistaken for
command-line options).
--cached
Use this option to unstage and remove paths only from the index. Working tree files, whether modified or not, will be left alone.
--ignore-unmatch
Exit with a zero status even if no files matched.
-q, --quiet
git rm normally outputs one line (in the form of an rm command) for each file removed. This option suppresses that output.
DISCUSSION
The <file> list given to the command can be exact pathnames, file glob patterns, or leading directory names. The command removes only the
paths that are known to Git. Giving the name of a file that you have not told Git about does not remove that file.
File globbing matches across directory boundaries. Thus, given two directories d and d2, there is a difference between using git rm 'd*'
and git rm 'd/*', as the former will also remove all of directory d2.
REMOVING FILES THAT HAVE DISAPPEARED FROM THE FILESYSTEM
There is no option for git rm to remove from the index only the paths that have disappeared from the filesystem. However, depending on the
use case, there are several ways that can be done.
Using "git commit -a"
If you intend that your next commit should record all modifications of tracked files in the working tree and record all removals of files
that have been removed from the working tree with rm (as opposed to git rm), use git commit -a, as it will automatically notice and record
all removals. You can also have a similar effect without committing by using git add -u.
Using "git add -A"
When accepting a new code drop for a vendor branch, you probably want to record both the removal of paths and additions of new paths as
well as modifications of existing paths.
Typically you would first remove all tracked files from the working tree using this command:
git ls-files -z | xargs -0 rm -f
and then untar the new code in the working tree. Alternately you could rsync the changes into the working tree.
After that, the easiest way to record all removals, additions, and modifications in the working tree is:
git add -A
See git-add(1).
Other ways
If all you really want to do is to remove from the index the files that are no longer present in the working tree (perhaps because your
working tree is dirty so that you cannot use git commit -a), use the following command:
git diff --name-only --diff-filter=D -z | xargs -0 git rm --cached
Submodules
Only submodules using a gitfile (which means they were cloned with a Git version 1.7.8 or newer) will be removed from the work tree, as
their repository lives inside the .git directory of the superproject. If a submodule (or one of those nested inside it) still uses a .git
directory, git rm will fail - no matter if forced or not - to protect the submodule's history.
A submodule is considered up-to-date when the HEAD is the same as recorded in the index, no tracked files are modified and no untracked
files that aren't ignored are present in the submodules work tree. Ignored files are deemed expendable and won't stop a submodule's work
tree from being removed.
If you only want to remove the local checkout of a submodule from your work tree without committing the removal, use git-submodule(1)
deinit instead.
EXAMPLES
git rm Documentation/*.txt
Removes all *.txt files from the index that are under the Documentation directory and any of its subdirectories.
Note that the asterisk * is quoted from the shell in this example; this lets Git, and not the shell, expand the pathnames of files and
subdirectories under the Documentation/ directory.
git rm -f git-*.sh
Because this example lets the shell expand the asterisk (i.e. you are listing the files explicitly), it does not remove
subdir/git-foo.sh.
SEE ALSO
git-add(1)
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-RM(1)