9 More Discussions You Might Find Interesting
1. Red Hat
Hi all,
I'm having this scenario which for the moment I cannot resolve. :(
I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example.
The script is like below:
cat /home/oracle/scripts/db_backup.sh
#!/bin/ksh
... (3 Replies)
Discussion started by: enux
3 Replies
2. Shell Programming and Scripting
Hello,
I was trying to identify lines who has a word of the following pattern "xyyx" (where x, and ys are different characters).
I was trying the following grep -
egrep '(\S)()\2\1'
This pattern do catches the wanted pattern, but it also catches "GGGG" or "CCCC" patterns. I was trying to... (5 Replies)
Discussion started by: itskov
5 Replies
3. HP-UX
Hi all,
I am using HP-UX and I have just noticed that when I log into the network it seems to save the previous windows that were subsequently closed on previous occasions. Does anyone know when I log in, it seems to display these previous windows, e.g. nedit windows open again?
Does... (1 Reply)
Discussion started by: cyberfrog
1 Replies
4. Shell Programming and Scripting
Hi All,
I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data.
If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But... (9 Replies)
Discussion started by: DILEEP410
9 Replies
5. Shell Programming and Scripting
Hi all,
I want to do a very simple thing with sed. I want to print out the line number of a disk I have defined in /etc/exports, so I do:
It's all good, but here's the problem. When I define md0 in a variable, I get nothing from sed:
Why is that? can anybody please help?
Thanks (2 Replies)
Discussion started by: alirezan
2 Replies
6. UNIX for Dummies Questions & Answers
Had a strange thing going on with my code. It's ok I figured it out for myself.... (2 Replies)
Discussion started by: mrpugster
2 Replies
7. UNIX for Advanced & Expert Users
As you are probably aware, $# indicates the number of parameters passed into a korn shell script. But this appears to hang around for
sunsequent runs...????
A simple script:-
#!/usr/bin/ksh
echo "#parameters $#"
echo "\$1 $1"
echo "\$2 $2"
I run the script with 0 parameters (all fine)
#... (7 Replies)
Discussion started by: gsw_aix
7 Replies
8. Shell Programming and Scripting
Can some-one give me a view to this :
I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory.
Now there is another directory basically the destination directory which has all the permissions.
Note:I log in as not the owner,but user... (5 Replies)
Discussion started by: navojit dutta
5 Replies
9. Linux
Hi there,
first of all, here is my conf of a uname -a
Linux SAMBA 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown
on a fedora machine.
Here is my problem: every once in a while, the line containing root disappears in the /etc/passwd, disabling all logging on my server. Any one have... (0 Replies)
Discussion started by: penguin-friend
0 Replies
TRS(1) Linux User's Manual TRS(1)
NAME
trs - filter replacing strings
SYNOPSIS
trs [-[r]e] 'REPLACE_THIS WITH_THAT [AND_THIS WITH_THAT]...'
trs [-[r]f] FILE
DESCRIPTION
Copy stdin to stdout replacing every occurence of given strings with other ones. This is similar to tr(1), but replaces strings, not only
single chars.
Rules (separated by whitespace) can be given directly after -e option, or can be read from FILE. Argument not preceded by -e or -f is
guessed to be a script when it contains some whitespace, or a filename otherwise.
Comments are allowed from # until the end of line. The character # in strings must be specified as #.
Standard C-like escapes a e f
v \
nn are recognized. In addition, s means a space character and ! means an empty
string.
Sets of acceptable characters at a given position can be specified between [ and ]. ASCII ranges in sets can be shortly written as
FIRST-LAST. When a set consists of only a single range, [ and ] can be omitted.
When a part of the string to translate is enclosed in {...}, only that part is replaced. Any text outside {...} serves as an assertion:
a string is translated only if it is preceded by the given text and followed by another one. { at the beginning or } at the end of the
string can be omitted. Text outside {...} is treated as untranslated.
Before the beginning of the file and after its end there are only
's. Thus, for example,
{.}
matches . on a line by itself,
including the first line, and the last one even without the
marker.
A fragment of the form ?x=N, where x is a letter A-Za-z and N is a digit 0-9, contained in the target text sets the variable x to the
value N when that rule succeeds. Similar fragment in the source text causes the given rule to be considered only if that variable has such
value. Initially all variables have the value of 0. Several assignments or conditions can be present in one rule - they are ANDed
together.
OPTIONS
-e Give the translation rules directly in the command line.
-f Get them from the file specified.
-r Reverse every rule. This affects only the next -e or -f option. Of course this doesn't have to give the reverse translation! Any
rule containing any of {}[]{}- is taken in only one direction. You may force any rule to be taken in only one direction by
enclosing the string to translate in {...}.
--help display help and exit
--version
output version information and exit
Multiple -e or -f options are allowed. All rules are loaded together then, and earlier ones have precedence.
EXAMPLE
$ echo Leeloo |trs -e 'el n e i i aqq o}
x o u'
Linux
DIFFERENCES FROM sed
The main difference between trs and sed 's///g; ...' (excluding sed's regular expressions) is that sed takes every rule in the order speci-
fied and applies it to the whole line of translated file, whereas trs examines every position and tries all rules in this place first. In
sed every next rule is fed with the text produced by the previous one, whereas in trs every piece of text can be translated at most once
(if more than one rule matches at a given position, the one mentioned earlier wins). That's why sed isn't well suited for translating
between character sets. On the other hand, tr translates only single bytes, so it can't be used for Unicode conversions, or TeX / SGML ways
for specifying extended characters.
Another example:
$ echo 642 |trs -e '4 7 72 66 64 4'
42
$ echo 642 |sed 's/4/7/g; s/72/66/g; s/64/4/g'
666
The string to replace can be empty; there must be something outside {} then. In this special case only one such create-from-nothing rule
can success at a given position. For example, }x80-xFF @ precedes every character with high byte set with @. The rule of the form
some{ thing doesn't work at the end of a file.
SEE ALSO
tr(1), konwert(1)
COPYRIGHT
trs is a filter replacing strings. It forms part of the konwert package.
Copyright (c) 1998 Marcin 'Qrczak' Kowalczyk
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation,
Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
AUTHOR
__("< Marcin Kowalczyk * qrczak@knm.org.pl http://qrczak.home.ml.org/
\__/ GCS/M d- s+:-- a21 C+++>+++$ UL++>++++$ P+++ L++>++++$ E->++
^^ W++ N+++ o? K? w(---) O? M- V? PS-- PE++ Y? PGP->+ t
QRCZAK 5? X- R tv-- b+>++ DI D- G+ e>++++ h! r--%>++ y-
Konwert 12 Jul 1998 TRS(1)