Sponsored Content
Top Forums Shell Programming and Scripting parsing config file to create new config files Post 302379599 by clazzic on Friday 11th of December 2009 06:50:38 AM
Old 12-11-2009
parsing config file to create new config files

Hi,

I want to use a config file as the base file and parse over the values of country and city parameters in the config file and generate separate config files as explained below.

I will be using the config file as mentioned below:
(config.txt)
Code:
country:a,b
city:1,2
type:b1
date:11-Dec-2009

I want to create config files as mentioned below:
(a_1.cfg)
Code:
country:a
city:1
type:b1
date:11-Dec-2009

(a_2.cfg)
Code:
country:a
city:2
type:b1
date:11-Dec-2009

(b_1.cfg)
Code:
country:b
 city:1
 type:b1
 date:11-Dec-2009

(b_2.cfg)
Code:
 country:b
  city:2
  type:b1
  date:11-Dec-2009

Any help is greatly appreciated!!!Smilie

Thx

Clazzic

Last edited by zaxxon; 12-11-2009 at 09:05 AM.. Reason: use code tags please, ty
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Parsing config file

Hi All, I have a requirement to parse a file. Let me clear you all on the req. I have a job which contains multiple tasks and each task will have multiple attributes that will be in the below format. Each task will have some sequence number according to that sequence number tasks shld... (0 Replies)
Discussion started by: rajeshorpu
0 Replies

2. UNIX for Dummies Questions & Answers

Issue with parsing config variables

I am using MKS tool kit on windows server. One config variable is defined in windows environment and I am trying to use that variable. # Below RootDir is defined in windows RootDir="\\f01\var" # in unix script details="$RootDir/src|$RootDir/tgt" src=`echo $details|awk -F '|' '{print... (1 Reply)
Discussion started by: madhukalyan
1 Replies

3. Shell Programming and Scripting

Need help parsing config file in ksh

Hi all, I've done some searching here but haven't found exactly what I'm looking for so I thought I'd post up and see if someone can help out. I'm working on a shell script that I would like to store environment variables in an external file. I'm familiar with sourcing a file with variables in... (1 Reply)
Discussion started by: kungfusnwbrdr
1 Replies

4. Shell Programming and Scripting

Parsing config-file (perl)

Hi, i'm trying to parse a config file that have alot of rows similar to this one: Example value value value What i want to do is to split and save the row above in a hash, like this: Example = value value value Basically i want to split on the first whitespace after the first... (3 Replies)
Discussion started by: mikemikemike
3 Replies

5. Shell Programming and Scripting

Shell script that will compare two config files and produce 2 outputs 1)actual config file 2)report

Hi I am new to shell scripting. There is a requirement to write a shell script to meet follwing needs.Prompt reply shall be highly appreciated. script that will compare two config files and produce 2 outputs - actual config file and a report indicating changes made. OS :Susi linux ver 10.3. ... (4 Replies)
Discussion started by: muraliinfy04
4 Replies

6. Shell Programming and Scripting

Parsing Nagios service config files with awk

Hope someone can help, I've been pulling my hair out with this one... I've written a shell script that does a sanity check on our quite extensive Nagios configuration for anything that needs cleaning up but wouldn't make the Nagios daemon necessarily bork or complain. One section of the script... (2 Replies)
Discussion started by: vinbob
2 Replies

7. Shell Programming and Scripting

parsing a config file using bash

Hi , I have a config _file that has 3 columns (Id Name Value ) with many rows . In my bash script i want to be able to parse the file and do a mapping of any Id value so if i have Id of say brand1 then i can use the name (server5X) and Value (CCCC) and so on ... Id Name ... (2 Replies)
Discussion started by: nano2
2 Replies

8. Shell Programming and Scripting

Merge multiple files found in config file

I have a config file with a bunch of these type of blocks: <concat destfile="${standard.js.file}" append="true"> <filelist dir="${js.dir}/foo" files="foo.js, foo2.js"/> <filelist dir="${js.dir}" files="foo3.js"/> <filelist dir="${js.dir}/bar/js"... (11 Replies)
Discussion started by: Validatorian
11 Replies

9. Red Hat

Apache virtual host config vs global config problem

Hi folks, I am trying to configure Apache webserver and also a virtual host inside this webserver. For Global server config: /var/www/html/index.html For virtual host config: /var/www/virtual/index.html Both client10 & www10 are pointing to 192.168.122.10 IP address. BUT, MY... (1 Reply)
Discussion started by: freebird8z
1 Replies

10. Windows & DOS: Issues & Discussions

(VS 2008) New build config looking files from other folder build config

Hi Team, My new build configuration always looking for the files from the build where i copied from. please help me to resolve this. I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
Regexp::Common::zip(3pm)				User Contributed Perl Documentation				  Regexp::Common::zip(3pm)

NAME
Regexp::Common::zip -- provide regexes for postal codes. SYNOPSIS
use Regexp::Common qw /zip/; while (<>) { /^$RE{zip}{Netherlands}$/ and print "Dutch postal code "; } DESCRIPTION
Please consult the manual of Regexp::Common for a general description of the works of this interface. Do not use this module directly, but load it via Regexp::Common. This module offers patterns for zip or postal codes of many different countries. They all have the form "$RE{zip}{Country}[{options}]". The following common options are used: "{-prefix=[yes|no|allow]}" and "{-country=PAT}". Postal codes can be prefixed with a country abbreviation. That is, a dutch postal code of 1234 AB can also be written as NL-1234 AB. By default, all the patterns will allow the prefixes. But this can be changed with the "-prefix" option. With "-prefix=yes", the returned pattern requires a country prefix, while "-prefix=no" disallows a prefix. Any argument that doesn't start with a "y" or a "n" allows a country prefix, but doesn't require them. The prefixes used are, unfortunally, not always the same. Officially, ISO country codes need to be used, but the usage of CEPT codes (the same ones as used on cars) is common too. By default, each postal code will recognize a country prefix that's either the ISO standard or the CEPT code. That is, German postal codes may prefixed with either "DE" or "D". The recognized prefix can be changed with the "-country" option, which takes a (sub)pattern as argument. The arguments "iso" and "cept" are special, and indicate the language prefix should be the ISO country code, or the CEPT code. Examples: /$RE{zip}{Netherlands}/; # Matches '1234 AB' and 'NL-1234 AB'. /$RE{zip}{Netherlands}{-prefix => 'no'}/; # Matches '1234 AB' but not 'NL-1234 AB'. /$RE{zip}{Netherlands}{-prefix => 'yes'}/; # Matches 'NL-1234 AB' but not '1234 AB'. /$RE{zip}{Germany}/; # Matches 'DE-12345' and 'D-12345'. /$RE{zip}{Germany}{-country => 'iso'}/; # Matches 'DE-12345' but not 'D-12345'. /$RE{zip}{Germany}{-country => 'cept'}/; # Matches 'D-12345' but not 'DE-12345'. /$RE{zip}{Germany}{-country => 'GER'}/; # Matches 'GER-12345'. "{-sep=PAT}" Some countries have postal codes that consist of two parts. Typically there is an official way of separating those parts; but in practise people tend to use different separators. For instance, if the official way to separate parts is to use a space, it happens that the space is left off. The "-sep" option can be given a pattern as argument which indicates what to use as a separator between the parts. Examples: /$RE{zip}{Netherlands}/; # Matches '1234 AB' but not '1234AB'. /$RE{zip}{Netherlands}{-sep => 's*'}/; # Matches '1234 AB' and '1234AB'. $RE{zip}{Australia} Returns a pattern that recognizes Australian postal codes. Australian postal codes consist of four digits; the first two digits, which range from '10' to '97', indicate the state. Territories use '02' or '08' as starting digits; the leading zero is optional. '0909' is the only postal code starting with '09' (the leading zero is optional here as well) - this is the postal code for the Nothern Territory University). The (optional) country prefixes are AU (ISO country code) and AUS (CEPT code). Regexp::Common 2.107 and before used $RE{zip}{Australia}. This is still supported. If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The state or territory. $5 The last two digits. $RE{zip}{Belgium} Returns a pattern than recognizes Belgian postal codes. Belgian postal codes consist of 4 digits, of which the first indicates the province. The (optional) country prefixes are BE (ISO country code) and B (CEPT code). If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The digit indicating the province. $5 The last three digits of the postal code. $RE{zip}{Denmark} Returns a pattern that recognizes Danish postal codes. Danish postal codes consist of four numbers; the first digit (which cannot be 0), indicates the distribution region, the second the distribution district. The (optional) country prefix is DK, which is both the ISO country code and the CEPT code. If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The digit indicating the distribution region. $5 The digit indicating the distribution district. $6 The last two digits of the postal code. $RE{zip}{France} Returns a pattern that recognizes French postal codes. French postal codes consist of five numbers; the first two numbers, which range from '01' to '98', indicate the department. The (optional) country prefixes are FR (ISO country code) and F (CEPT code). Regexp::Common 2.107 and before used $RE{zip}{French}. This is still supported. If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The department. $5 The last three digits. $RE{zip}{Germany} Returns a pattern that recognizes German postal codes. German postal codes consist of five numbers; the first number indicating the distribution zone, the second the distribution region, while the latter three indicate the distribution district and the postal town. The (optional) country prefixes are DE (ISO country code) and D (CEPT code). Regexp::Common 2.107 and before used $RE{zip}{German}. This is still supported. If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The distribution zone. $5 The distribution region. $6 The distribution district and postal town. $RE{zip}{Greenland} Returns a pattern that recognizes postal codes from Greenland. Greenland, being part of Denmark, uses Danish postal codes. All postal codes of Greenland start with 39. The (optional) country prefix is DK, which is both the ISO country code and the CEPT code. If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 39, being the distribution region and distribution district for Greenland. $5 The last two digits of the postal code. $RE{zip}{Italy} Returns a pattern recognizing Italian postal codes. Italian postal codes consist of 5 digits. The first digit indicates the region, the second the province. The third digit is odd for province capitals, and even for the province itself. The fourth digit indicates the route, and the fifth a place on the route (0 for small places, alphabetically for the rest). The country prefix is either IT (the ISO country code), or I (the CEPT code). If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The region. $5 The province. $6 Capital or province. $7 The route. $8 The place on the route. $RE{zip}{Netherlands} Returns a pattern that recognizes Dutch postal codes. Dutch postal codes consist of 4 digits and 2 letters, separated by a space. The separator can be changed using the "{-sep}" option, as discussed above. The (optional) country prefix is NL, which is both the ISO country code and the CEPT code. Regexp::Common 2.107 and earlier used $RE{zip}{Dutch}. This is still supported. If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The digits part of the postal code. $5 The separator between the digits and the letters. $6 The letters part of the postal code. $RE{zip}{Norway} Returns a pattern that recognizes Norwegian postal codes. Norwegian postal codes consist of four digits. The country prefix is either NO (the ISO country code), or N (the CEPT code). If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $RE{zip}{Spain} Returns a pattern that recognizes Spanish postal codes. Spanish postal codes consist of 5 digits. The first 2 indicate one of Spains fifties provinces (in alphabetical order), starting with 00. The third digit indicates a main city or the main delivery rounds. The last two digits are the delivery area, secondary delivery route or a link to rural areas. The country prefix is either ES (the ISO country code), or E (the CEPT code). If "{-keep}" is used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The two digits indicating the province. $5 The digit indicating the main city or main delivery route. $6 The digits indicating the delivery area, secondary delivery route or a link to rural areas. $RE{zip}{Switzerland} Returns a pattern that recognizes Swiss postal codes. Swiss postal codes consist of 4 digits. The first indicates the district, starting with 1. The second indicates the area, the third, the route, and the fourth the post office number. $RE{zip}{US}{-extended => [yes|no|allow]} Returns a pattern that recognizes US zip codes. US zip codes consist of 5 digits, with an optional 4 digit extension. By default, extensions are allowed, but not required. This can be influenced by the "-extended" option. If its argument starts with a "y", extensions are required; if the argument starts with a "n", extensions will not be recognized. If an extension is used, a dash is used to separate the main part from the extension, but this can be changed with the "-sep" option. The country prefix is either US (the ISO country code), or USA (the CEPT code). If "{-keep}" is being used, the following variables will be set: $1 The entire postal code. $2 The country code prefix. $3 The postal code without the country prefix. $4 The first 5 digits of the postal code. $5 The first three digits of the postal code, indicating a sectional center or a large city. New in Regexp::Common 2.119. $6 The last 2 digits of the 5 digit part of the postal code, indicating a post office facility or delivery area. New in Regexp::Common 2.119. $7 The separator between the 5 digit part and the 4 digit part. Up to Regexp::Common 2.118, this used to be $5. $8 The 4 digit part of the postal code (if any). Up to Regexp::Common 2.118, this used to be $6. $9 The first two digits of the 4 digit part of the postal code, indicating a sector, or several blocks. New in Regexp::Common 2.119. $10 The last two digits of the 4 digit part of the postal code, indicating a segment or one side of a street. New in Regexp::Common 2.119. You need at least version 5.005_03 to be able to use US postal codes. Older versions contain a bug that let the pattern match invalid US postal codes. Questions o Can the 5 digit part of the zip code (in theory) start with 000? o Can the 5 digit part of the zip code (in theory) end with 00? o Can the 4 digit part of the zip code (in theory) start with 00? o Can the 4 digit part of the zip code (in theory) end with 00? SEE ALSO
Regexp::Common for a general description of how to use this interface. <http://www.columbia.edu/kermit/postal.html> Frank's compulsive guide to postal addresses. <http://www.upu.int/post_code/en/addressing_formats_guide.shtml> Postal addressing systems. http://www.uni-koeln.de/~arcd2/33e.htm <http://www.uni-koeln.de/~arcd2/33e.htm> Postal code information. <http://www.grcdi.nl/linkspc.htm> Links to Postcode Pages. <http://www1.auspost.com.au/postcodes/> Information about Australian postal codes. http://hdusps.esecurecare.net/cgi-bin/hdusps.cfg/php/enduser/std_adp.php?p_faqid=1014 <http://hdusps.esecurecare.net/cgi- bin/hdusps.cfg/php/enduser/std_adp.php?p_faqid=1014> Information about US postal codes. <http://en.wikipedia.org/wiki/Postal_code> AUTHORS
Damian Conway (damian@conway.org) and Abigail (regexp-common@abigail.be). MAINTAINANCE
This package is maintained by Abigail (regexp-common@abigail.be). BUGS AND IRRITATIONS
Zip codes for most countries are missing. Send them in to regexp-common@abigail.be. LICENSE and COPYRIGHT This software is Copyright (c) 2001 - 2009, Damian Conway and Abigail. This module is free software, and maybe used under any of the following licenses: 1) The Perl Artistic License. See the file COPYRIGHT.AL. 2) The Perl Artistic License 2.0. See the file COPYRIGHT.AL2. 3) The BSD Licence. See the file COPYRIGHT.BSD. 4) The MIT Licence. See the file COPYRIGHT.MIT. perl v5.14.2 2010-02-23 Regexp::Common::zip(3pm)
All times are GMT -4. The time now is 09:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy