I use many different machines at work, each with different versions of o/s's and installed applications. Sed in vi is particularly inconvenient in the sense that sometimes it will accept the "\r" as a carriage return, sometimes not. Same thing with "\n". For instance, if I have a list of hosts that are all on one line separated by a space then I need them in line-by-line format. On some machines I can do this in vi:
or
I don't know if the editor will accept \r or \n until I try. On some machines it will treat either as a regular character by inserting an "r" or "n" in place of the spaces. Is this relative to my version of vi, o/s, sed, or all? I'm assuming \r and \n are ASCII characters. Is there a chance the ASCII chars are defined differently depending on the o/s? (I thought it was a standard) How can I determine in advance which host will accept \r or \n as carriage return and newline, respectively, before I start vi?
I do not have the authorisation to upgrade the o/s or editors to the latest versions.
hi,
I have this script which gives me the result...
#! /usr/bin/sh
set -x
cd /home/managar
a=1
while true
do
if
then
echo " File log.txt exists in this directory "
exit 0
fi
echo " File has not arrived yes..."
sleep 3
let a=a+1
if
then (1 Reply)
I have written a shell script which looks like below:
grep -v ',0,' ./DATA/abc.001 > ./DATA/abc.mid
egrep $GREPSEARCH ./DATA/ebc.mid > ./DATA/abc.cut
the variable GREPSEARCH has values like the below:
... (3 Replies)
Hi,
I have a script in which an entry like this .....
FILENAME_B="PIC_${DATE}0732*.JPG"
The script connects to an ATM and pull a pic file from it.The format for the file is like PIC_2008061400000001.JPG in the ATM.
Means 1st 8 digit is the date(YYYYMMDD) field
2nd 8 digit means hrs... (2 Replies)
Hi all
Here I came accross a situation which i am unable to reason out...
snippet 1
psg ServTest | grep -v "grep" | grep -v "vi" | awk '{
pgm_name=$8
cmd_name="ServTest"
gsub(/]*/,"",pgm_name)
if(pgm_name==cmd_name) { print "ServTest Present =" cmd_name}
}'... (10 Replies)
Hi All
I have a flat text file. Each line in it contains a "/full path/filename". The last three columns are predictable, but directory depth of each line varies.
I want to sort on the last three columns, starting from the last, 2nd last and 3rd last. In that order. The last three columns... (6 Replies)
Hi,
I am using HP-UX B.11.23 U ia64
I am trying to retrieve files using -mtime option of find command
However I found that -mtime is not giving correct results
Following is the output of commands executed on 03-Dec-2009
It can be seen that -mtime +1 should have returned all... (2 Replies)
Hello,
I am writing a small one liner script to display the tables in my database.
I am working with Centos 5.5 and postgresql
the command is
"psql -c "\dt" | awk '{print$3}'"
I just want the 3rd column from the result set, but now the problem is I am getting the third column but with... (3 Replies)
Version: RHEL 5.8
I am doing a grep of the piped output from ps command as shown below.
I am grepping for the pattern ora_dbw* . But, in the result set I am seeing strings with ora_dbr* as well like ora_dbrm_SDLM1DAS3 as shown below. Any idea why is this happening ?
$ ps -ef | grep... (6 Replies)
Hi,
I am running a script sample.sh in bash environment .In the script i am using sed and awk commands which when executed individually from terminal they are getting executed normally but when i give these sed and awk commands in the script it is giving the below errors :-
./sample.sh: line... (12 Replies)
Hi
I am comparing two files with comm -13 < (sort acc11.txt) < (sort acc12.txt) > output.txt
purpose: Get non matching records which are in acc12 but not in acc11...
TI am getting WRONG output.
Is there any constraints with record length with comm? The above files are the two consective ... (2 Replies)
Discussion started by: vedanta
2 Replies
LEARN ABOUT DEBIAN
tsi
TSI(5) File Formats Manual TSI(5)NAME
tsi - Transmission Subscriber Identification (TSI) access control list
DESCRIPTION
The HylaFAX configuration parameter QualifyTSI specifies whether or not the identity of a calling facsimile machine should be checked
against an access control list before receiving facsimile. If QualifyTSI is non-null, then only messages from facsimile machines identi-
fied in the file specified by the string (typically etc/tsi) will be accepted.
Patterns are specified one per line and must conform to the regular expressions syntax specified by POSIX 1003.2; see re_format(7). Com-
ments may be included; they are introduced with the ``#'' character and extend to the end of the line. Any trailing white space on a line
is ignored (for convenience when comments are used).
If a line begins with ``!'', then the regular expression identifies clients that should be rejected; otherwise regular expressions identify
clients whose transmissions should be accepted. The order of patterns in a TSI file is important. When a facsimile is to be received, the
fax server will compare the client's TSI against the patterns in the access control list in the order in which they appear in the file.
The first pattern that matches the client TSI is used to decide whether to accept or reject the facsimile. If no patterns match the client
TSI then the facsimile is rejected. Thus if you want to accept all but a restricted set of TSI the last line in the file should be
``^.*$''.
Note that regular expression patterns should be written to match a TSI exactly. That is, patterns should be of the form:
^<pattern>$
where the ``^'' and ``$'' characters are used to specify the start and end of the matching TSI. Additionally, regular expression patterns
should handle white space that may appear in known locations. For example,
^([+]1){1}[ .-]*415[ .-]*555[ .-]*1212.*$
matches the following TSI strings:
+1.415.555.1212
415 555 1212
1-415-555-1212
Finally, note that regular expressions can be used to specify many TSI with one pattern.
NOTES
It would be nice if TSI that were to be matched against were placed in some canonical form (e.g. remove white space and white space-like
characters). This is, however, problematic, because some facsimile machines permit any printable ASCII string to be sent as a TSI.
SEE ALSO faxgetty(8), re_format(7), hylafax-config(5)
December 5, 1994 TSI(5)