05-27-2014
In addition to what RudiC said in the previous post, it is also interesting to note that the "|" between fields 2 and 3 was described in post #3 in this thread as an embedded character (that needed to be changed) in the 2nd field rather than a separator between fields.
The problem described in the original posting has been solved long ago.
The new problem has been inconsistently and incompletely described.
This thread is closed.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am using sed to replace things like "," and tabs in a file, but what is the code for replacing a \ ???? (5 Replies)
Discussion started by: rjsha1
5 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I am facing a strange situation and want to find why it is occuring . When i convert the whole line into Hexadecimal character i can find the junk value after new line (\n) . If i look in binary mode it is not visible.
PLease let me know how possible the junk character is added... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
3. Shell Programming and Scripting
Hi All,
I'm trying to write a ksh script to parse a file. When the "\" character is encountered, it should be removed and the next line should be concatenated with the current line. For example...
this is a test
line #1\
should be concatenated with line #2\
and line number 3
when this... (3 Replies)
Discussion started by: newbie_coder
3 Replies
4. UNIX for Dummies Questions & Answers
Hi!!..
I would like to know what is maximum character size for a command in the "sh" or "bourne" shell?
Thanks in advance..
Roshan. (1 Reply)
Discussion started by: Roshan1286
1 Replies
5. UNIX for Advanced & Expert Users
Hi!!..
I would like to know what is maximum character size for a command in the "sh" or "bourne" shell?
Thanks in advance..
Roshan. (1 Reply)
Discussion started by: Roshan1286
1 Replies
6. Shell Programming and Scripting
Hi!!..
I would like to know what is maximum character size for a command in the "sh" or "bourne" shell?
Thanks in advance..
Roshan. (1 Reply)
Discussion started by: Roshan1286
1 Replies
7. Shell Programming and Scripting
Hi,
My input has much more lines, but few of them are below
pin(IDF) {
direction : input;
drc_pinsigtype : signal;
pin(SELDIV6) {
direction : input;
drc_pinsigtype : ... (3 Replies)
Discussion started by: nehashine
3 Replies
8. Shell Programming and Scripting
Hello everyone
Sorry I have to add another sed question. I am searching a log file and need only the first 2 occurances of text which comes after (note the space) "string " and before a ",". I have tried
sed -n 's/.*string \(*\),.*/\1/p' filewith some, but limited success. This gives out all... (10 Replies)
Discussion started by: haggismn
10 Replies
9. UNIX for Dummies Questions & Answers
Hi All
It's me again with another huge txt files. :confused:
What I have:
- I have 33 huge txt files in a folder.
- I have thousands of line in this txt file which contain many the letter "x" in them.
- Some of them have more than one "x" character in the line.
What I want to achieve:... (8 Replies)
Discussion started by: Nexeu
8 Replies
10. Shell Programming and Scripting
I'd like to put paragraph breaks \n\n randomly between 5 - 10 occurrences of the dot character (.), for an entire text file. How to do that?
In other words, anywhere between every 5 -10 sentences, a new paragraph will generate. There are no other uses of the (.) except for sentence breaks in... (11 Replies)
Discussion started by: p1ne
11 Replies
LEARN ABOUT DEBIAN
nnrp.access
NNRP.ACCESS(5) File Formats Manual NNRP.ACCESS(5)
NAME
nnrp.access - access file for on-campus NNTP sites
DESCRIPTION
The file /etc/news/nnrp.access specifies the access control for those NNTP sites that are not handled by the main InterNetNews daemon
innd(8). The nnrpd(8) server reads it when first spawned by innd.
Comments begin with a number sign (``#'') and continue through the end of the line. Blank lines and comments are ignored. All other lines
should consist of five fields separated by colons:
hosts:perms:username:password:patterns
The first field is a wildmat(3)-style pattern specifying the names or Internet address of a set of hosts. Before a match is checked, the
client's hostname (or its Internet address if gethostbyaddr(3) fails) is converted to lowercase. Each line is matched in turn, and the
last successful match is taken as the correct one.
The second field is a set of letters specifying the permissions granted to the client. The perms should be chosen from the following set:
R The client can retrieve articles
P The client can post articles
The third and fourth fields specify the username and password that the client must use to authenticate themselves before the server will
accept any articles. Note that no authentication (other then a matching entry in this file) is required for newsreading. If they are
empty, then no password is required. Whitespace in these fields will result in the client being unable to properly authenticate themselves
and may be used to disable access.
The fifth field is a set of patterns identifying the newsgroups that the client is allowed to access. The patterns are interpreted in the
same manner as the newsfeeds(5) file. The default, however, denies access to all groups.
The access file is normally used to provide host-level access control for reading and posting articles. There are times, however, when
this is not sufficient and user-level access control is needed. Whenever an NNTP ``authinfo'' command is used, the nnrpd server re-reads
this file and looks for a matching username and password. If the local newsreaders are modified to send the ``authinfo'' command, then all
host entries can have no access and specific users can be granted the appropriate read and post access.
For example:
## host:perm:user:pass:groups
## Default is no access.
*:: -no- : -no- :!*
## FOO hosts have no password, can read anything.
*.foo.com:Read Post:::*
## A related workstation can't access FOO newsgroups.
lenox.foo.net:RP:martha:hiatt:*,!foo.*
If the file contains passwords, it should not be world-readable.
HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 1.11, dated 1996/09/06.
SEE ALSO
innd(8), newsfeeds(5), nnrpd(8), wildmat(3).
NNRP.ACCESS(5)