![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Automate FTP | borncrazy | Shell Programming and Scripting | 11 | 02-21-2008 12:10 AM |
| How to automate an FTP process? | ksak | Shell Programming and Scripting | 1 | 10-06-2006 12:45 PM |
| Automate FTP | CamTu | UNIX for Advanced & Expert Users | 4 | 02-25-2005 10:08 AM |
| automate useradd | steffa | Shell Programming and Scripting | 1 | 09-14-2004 04:33 PM |
| automate an ftp job | flowrats | UNIX for Dummies Questions & Answers | 11 | 07-24-2002 08:47 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Hi All,
I have stooopidly agreed to automate our release process (which though easy is a pain). The config file has a simple structure, below, each section can have upto 20 parms. The release doc will have the section name and parm to be changed. What I want is to read the list of changes and then make the edit. I can do the auto edit (done before) I'm just struggling to do the find and read next line. I'll find the section name and then read then next lot of lines, make the edits and do this until I find the next section name , where I start the edits again. I'm finding the section based on the "^[" but I'm not sure how to continue the read assuming the ^ not equal to ^[. Any ideas????? [Section1] parm=value parm2=value parm3=value [Section2] parm=value parm2=value parm3=value |
|
||||
|
This might get you started.
I assume the config file and the changes file have the same format. I also assume the changes file is a subset of the config file. You could convert both of them to a different format. e.g. nawk '/\[.*\]/ { SECT=$1; next } { print SECT$0 }' configfile > tmpfile1 nawk '/\[.*\]/ { SECT=$1; next } { print SECT$0 }' changesfile > tmpfile2 Use info from tmpfile2 to make changes in tmpfile1. When done convert tmpfile1 back to original format and use this file to replace the original config file. running the command above on the example config file you provided would result in the following output: tmpfile1: [Section1]parm=value [Section1]parm2=value [Section1]parm3=value [Section2]parm=value [Section2]parm2=value [Section2]parm3=value Suppose your changes file looks like: [Section1] parm2=newvalue1 [Section2] parm=newvalue2 Again using the command above the output would be: tmpfile2: [Section1]parm2=newvalue1 [Section2]parm=newvalue Thsi puts the config and changes file in a similar format which makes it easy to make the necessary edits. As mentioned, when the edits are done convert the format back. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|