First thanx for the reply. I think I was not clear in my question. There will be n number of lines besides
which also contains
But my requirement is I have to extract those lines which have string "sasl_username=anything@xyz.com" from the logs. I hope this time I am clear
Hi
I have a pattern like :
SYSTEM_NAME-232-S7-200810060949.LOG
Here I need to extract system name and the timestamp and also the numeric number after "-S" i.e 7 here .
I am not very sure of whether I should use sed / awk for this ?:confused:
Thanks,
Priya. (6 Replies)
This is my first post, please be nice. I have tried to google and read different tutorials.
The task at hand is:
Input file input.txt (example)
abc123defhij-E-1234jslo
456ujs-W-abXjklp
From this file the task is to grep the -E- and -W- strings that are unique and write a new file... (5 Replies)
Hi all,
I am trying to extract the values ( text between the xml tags) based on the Order Number.
here is the sample input
<?xml version="1.0" encoding="UTF-8"?>
<NJCustomer>
<Header>
<MessageIdentifier>Y504173382</MessageIdentifier>
... (13 Replies)
I have hundreds of files to process. In each file
I need to look for a pattern then
extract value(s) from next line and then
search for value(s) selected from point (2) in the same file at a specific position.
HEADER ELECTRON TRANSPORT 18-MAR-98 1A7V
TITLE CYTOCHROME... (7 Replies)
Hi,
I am able to get next line if it is matching a particular pattern. But i need a way to skip if next line also matches same pattern..
For example:
No Records
No Records
Records found
got it
Records found
Now i want to find 'Records found' after 'No Records' pattern matches..
... (5 Replies)
Hi there, I am pretty new to those things, so I couldn't figure out how to solve this, and if it is actually that easy. just found that awk could help:(.
so i have a textfile with strings and numbers (originally copy pasted from word, therefore some empty cells) in the following structure:
SC... (9 Replies)
I want to extract dates from the files and i have different types of files with pattern. I have list file with the patterns and want to date extract based on it in a sh script
Files in the directory :
file1_20160101.txt
file2_20160101_abc.txt
filexyz20160101.txt
list file with... (2 Replies)
Hello All,
I have multiple files in a hadoop /tmp/cloudera directory.
Filename are as follows
ABC_DATA_BAD5A_RO_F_20161104.CSV
ABC_DATA_BAD6C_VR_F_20161202.CSV
ABC_DATA_BAD7A_TR_F_20162104.CSV
ABC_DATA_BAD2A_BR_F_20161803.CSV
ABC_DATA_BAD3T_KT_F_20160106.CSV
I just need filenames... (6 Replies)
Hi All,
i would like to get some help regarding extracting certain characters from a line grepped.
blahblah{1:F01IRVTUS30XXXX0000000001}{2:I103IRVTDEF0XXXXN}{4:blah
blahblah{1:F01IRVTUS30XXXX0000000001}{2:I103IRVTDEF0XXXXN}{4:blah... (10 Replies)
Hello.
Here is a file contents :
declare -Ax NEW_FORCE_IGNORE_ARRAY=(="§" ="§" ="§" ="§" ="§" .................. ="§"Here is a pattern
=I want to extract 'NEW_FORCE_IGNORE_ARRAY' which is the whole word before the first occurrence of pattern '='
Is there a better solution than mine :... (3 Replies)
Discussion started by: jcdole
3 Replies
LEARN ABOUT DEBIAN
radiusd.conf
radiusd.conf(5) FreeRADIUS configuration file radiusd.conf(5)NAME
radiusd.conf - configuration file for the FreeRADIUS server
DESCRIPTION
The radiusd.conf file resides in the radius database directory, by default /etc/raddb. It defines the global configuration for the FreeRA-
DIUS RADIUS server.
CONTENTS
There are a large number of configuration parameters for the server. Most are documented in the file itself as comments. This page docu-
ments only the format of the file. Please read the radiusd.conf file itself for more information.
The configuration file parser is independent of the server configuration. This means that you can put almost anything into the configura-
tion file. So long as it is properly formatted, the server will start.
When the server parses the configuration file, it looks only for those configurations it understands. Extra configuration items are
ignored. This "feature" can be (ab)used in certain interesting ways.
FILE FORMAT
The file format is line-based, like many other Unix configuration files. Each entry in the file must be placed on a line by itself,
although continuations are supported.
The file consists of configuration items (variable = value pairs), sections, and comments.
Variables
Variables can be set via:
name = value
Single and double-quoted strings are permitted:
string1 = "hello world"
string2 = 'hello mom'
Sections
A section begins with a section name, followed on the same line by an open bracket '{'. Section may contain other sections, com-
ments, or variables. Sections may be nested to any depth, limited only by available memory. A section ends with a close bracket
'}', on a line by itself.
section {
...
}
Sections can sometimes have a second name following the first one. The situations where this is legal depend on the context. See
the examples and comments in the radiusd.conf file for more information.
section foo {
...
}
Comments
Any line beginning with a (#) is deemed to be a comment, and is ignored. Comments can appear after a variable or section defini-
tions.
# comment
foo = bar # set variable 'foo' to value 'bar'
section { # start of section
...
} # end of section
Continuations
Long lines can be broken up via continuations, using '' as the last character of the line. For example, the following entry:
foo = "blah
blah
blah"
will set the value of the variable "foo" to "blah blah blah". Any CR or LF is not turned into a space, but all other whitespace is
preserved in the final value.
REFERENCES
The value of a variable can reference another variable. These references are evaluated when the configuration file is loaded, which means
that there is no run-time cost associated with them. This feature is most useful for turning long, repeated pieces of text into short
ones.
Variables are referenced by ${variable_name}, as in the following examples.
foo = bar # set variable 'foo' to value 'bar'
who = ${foo} # sets variable 'who' to value of variable 'foo'
my = "${foo} a" # sets variable 'my' to "bar a"
If the variable exists in a section or subsection, it can be referenced as ${section.subsection.variable}. Forward references are not
allowed. Relative references are allowed, by pre-pending the name with one or more period.
blogs = ${.foo}
Will set variable blogs to the value of variable foo, from the current section.
blogs = ${..foo}
Will set variable blogs to the value of variable foo, from the section which contains the current section.
blogs = ${modules.detail.detailfile}
Will set variable blogs to the value of variable detailfile, of the detail module, which is in the modules section of the configuration
file.
FILES
/etc/raddb/radiusd.conf
SEE ALSO radiusd(8)unlang(5)AUTHOR
Alan DeKok <aland@freeradius.org>
12 Jun 2007 radiusd.conf(5)