10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello guys,
I have problem with hpux shell script. I have one big text file that contains like
SOH
bla bla bla
bla bla bla
ETX SOH
bla bla bla
ETX
SOH
bla bla bla
ETX
What I need to do is save first SOH*BLA into file1.txt, save second SOH*BLA into file2.txt and so on.... (17 Replies)
Discussion started by: sembii
17 Replies
2. Shell Programming and Scripting
Hi Team
I have an huge xml where i need to search for a ceratin numbers. For example
2014-05-06 15:15:41,498 INFO WebContainer : 10 CommonServicesLogs - CleansingTriggerService.invokeCleansingService Entered PUBSUB NOTIFY MESSAGE () -
<?xml version="1.0" encoding="UTF-8"... (5 Replies)
Discussion started by: Kannannair
5 Replies
3. Shell Programming and Scripting
Need Assistance in shell programming... I have a huge file which has multiple stations and i wanted to search particular station and extract few lines from it and the rest is not needed
Bold letters are the stations . The whole file has multiple stations .
Below example i wanted to search... (4 Replies)
Discussion started by: ajayram_arya
4 Replies
4. Shell Programming and Scripting
I have a file with below contents.
INCLUDE
INCLUDE SYSLIB(SANJ)
INCLUDE SYSLIB(BIS)
NAME BQTFL(R)
dfdg fgbb NAME B
i want to grep for "INCLUDE SYSLIB" in the file and do some operation so that my output will be in the bracketed value as below.
SANJ
BIS
Pls let me know how can i... (7 Replies)
Discussion started by: millan
7 Replies
5. Shell Programming and Scripting
Hi i am having a logfile which contain lot of entires, but i need extract a word after if i found a line that contains a particular string as "ENROLLMENT_EXCEPTION - Exception". please help me in getting a script to do this.
Regards
C. Suresh (5 Replies)
Discussion started by: sumeeva1907
5 Replies
6. Shell Programming and Scripting
Hi,
Here is my question,
I need to extract string between two underscores from the filename
for example, filename is
atmos_8xdaily_instant_300x300_1_12.nc
what I want to extract is 300x300.
There are many such files in my directory, so I guess the code should be like:
for file... (7 Replies)
Discussion started by: 1988PF
7 Replies
7. Shell Programming and Scripting
continuing from my previous post, whose link is given below as a reference
https://www.unix.com/shell-programming-scripting/171076-shell-scripting.html#post302573569
consider there is create table commands in a file for eg:
CREATE TABLE `Blahblahblah` (
`id` int(11) NOT NULL... (2 Replies)
Discussion started by: vivek d r
2 Replies
8. Shell Programming and Scripting
Below are the content of my file and i need to extract the 6 digit numbers after the word barcode, how can i do this?
for example i need to extract 004119,004275,004030 to a new file.
Logically move media ID 004119 (barcode 004119) from standalone to slot 18.
Logically move media ID 004275... (9 Replies)
Discussion started by: shehzad_m
9 Replies
9. Shell Programming and Scripting
Hi, guys. I have one question:
I need to search for a string in a file, and then extract another string from the file and assign it to a variable.
For example:
the contents of the file (group) is below:
...
ftp:x:23:
mail:x:34
...
testing:x:2001
sales:x:2002
development:x:2003
...... (6 Replies)
Discussion started by: daikeyang
6 Replies
10. Shell Programming and Scripting
Input File:
=====================================
"Server1" srvgrp="group1" srvid=10
CLOPT="-A -r -e /path/logfile -o /path/stdout"
VAR1=0666 VAR2=N VAR3=0666 MIN=3 VAR4=4 VAR5=N
VAR6=FASTPATH
VAR7=5 VAR8=86400 VAR9=Y
... (20 Replies)
Discussion started by: kaustubh137
20 Replies
GIT-UPDATE-REF(1) Git Manual GIT-UPDATE-REF(1)
NAME
git-update-ref - Update the object name stored in a ref safely
SYNOPSIS
git update-ref [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>] | --stdin [-z])
DESCRIPTION
Given two arguments, stores the <newvalue> in the <ref>, possibly dereferencing the symbolic refs. E.g. git update-ref HEAD <newvalue>
updates the current branch head to the new object.
Given three arguments, stores the <newvalue> in the <ref>, possibly dereferencing the symbolic refs, after verifying that the current value
of the <ref> matches <oldvalue>. E.g. git update-ref refs/heads/master <newvalue> <oldvalue> updates the master branch head to <newvalue>
only if its current value is <oldvalue>. You can specify 40 "0" or an empty string as <oldvalue> to make sure that the ref you are creating
does not exist.
It also allows a "ref" file to be a symbolic pointer to another ref file by starting with the four-byte header sequence of "ref:".
More importantly, it allows the update of a ref file to follow these symbolic pointers, whether they are symlinks or these "regular file
symbolic refs". It follows real symlinks only if they start with "refs/": otherwise it will just try to read them and update them as a
regular file (i.e. it will allow the filesystem to follow them, but will overwrite such a symlink to somewhere else with a regular
filename).
If --no-deref is given, <ref> itself is overwritten, rather than the result of following the symbolic pointers.
In general, using
git update-ref HEAD "$head"
should be a lot safer than doing
echo "$head" > "$GIT_DIR/HEAD"
both from a symlink following standpoint and an error checking standpoint. The "refs/" rule for symlinks means that symlinks that point to
"outside" the tree are safe: they'll be followed for reading but not for writing (so we'll never write through a ref symlink to some other
tree, if you have copied a whole archive by creating a symlink tree).
With -d flag, it deletes the named <ref> after verifying it still contains <oldvalue>.
With --stdin, update-ref reads instructions from standard input and performs all modifications together. Specify commands of the form:
update SP <ref> SP <newvalue> [SP <oldvalue>] LF
create SP <ref> SP <newvalue> LF
delete SP <ref> [SP <oldvalue>] LF
verify SP <ref> [SP <oldvalue>] LF
option SP <opt> LF
Quote fields containing whitespace as if they were strings in C source code. Alternatively, use -z to specify commands without quoting:
update SP <ref> NUL <newvalue> NUL [<oldvalue>] NUL
create SP <ref> NUL <newvalue> NUL
delete SP <ref> NUL [<oldvalue>] NUL
verify SP <ref> NUL [<oldvalue>] NUL
option SP <opt> NUL
Lines of any other format or a repeated <ref> produce an error. Command meanings are:
update
Set <ref> to <newvalue> after verifying <oldvalue>, if given. Specify a zero <newvalue> to ensure the ref does not exist after the
update and/or a zero <oldvalue> to make sure the ref does not exist before the update.
create
Create <ref> with <newvalue> after verifying it does not exist. The given <newvalue> may not be zero.
delete
Delete <ref> after verifying it exists with <oldvalue>, if given. If given, <oldvalue> may not be zero.
verify
Verify <ref> against <oldvalue> but do not change it. If <oldvalue> zero or missing, the ref must not exist.
option
Modify behavior of the next command naming a <ref>. The only valid option is no-deref to avoid dereferencing a symbolic ref.
Use 40 "0" or the empty string to specify a zero value, except that with -z an empty <oldvalue> is considered missing.
If all <ref>s can be locked with matching <oldvalue>s simultaneously, all modifications are performed. Otherwise, no modifications are
performed. Note that while each individual <ref> is updated or deleted atomically, a concurrent reader may still see a subset of the
modifications.
LOGGING UPDATES
If config parameter "core.logAllRefUpdates" is true and the ref is one under "refs/heads/", "refs/remotes/", "refs/notes/", or the symbolic
ref HEAD; or the file "$GIT_DIR/logs/<ref>" exists then git update-ref will append a line to the log file "$GIT_DIR/logs/<ref>"
(dereferencing all symbolic refs before creating the log name) describing the change in ref value. Log lines are formatted as:
1. oldsha1 SP newsha1 SP committer LF
Where "oldsha1" is the 40 character hexadecimal value previously stored in <ref>, "newsha1" is the 40 character hexadecimal value of
<newvalue> and "committer" is the committer's name, email address and date in the standard Git committer ident format.
Optionally with -m:
1. oldsha1 SP newsha1 SP committer TAB message LF
Where all fields are as described above and "message" is the value supplied to the -m option.
An update will fail (without changing <ref>) if the current user is unable to create a new log file, append to the existing log file or
does not have committer information available.
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-UPDATE-REF(1)