b49b
![]() |
|
|
|
|
|||||||
| Userland Programming & Scripting C, Shell, Perl, Sed & Awk |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Hi there,
I want to write a rc script. My rc.conf should hold information for it in following format: Code:
md_enable="YES" md_file_md0="/path/to/file-0" md_file_md1="/path/to/file-1" md_file_md2="/path/to/file-2" Code:
for FILE in $md_file_md*; do
echo $FILE
done
Thanks |
|
#2
|
||||
|
||||
|
Why not to set
Code:
md_files="/path/to/file-0 /path/to/file-1 /path/to/file-2" |
|
#3
|
|||
|
|||
|
Thanks for your input. I thought about such a solution already but the issue is that this method would not relate md dev number with file definition ... So it is not really usable for my needs.
|
|
#4
|
|||
|
|||
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Restart the script in newsyslog.conf | oksidant | General | 1 | January 20th, 2012 08:08 |
| sh -> vars in [ -a ] aren't evalueated correctly | Seeker | Userland Programming & Scripting | 11 | November 13th, 2011 18:44 |
| Odd behaviour related to rc.conf | gman88 | Web & Network Services | 3 | July 23rd, 2010 00:54 |
| Python script which checks for syntax error in rc.conf | Kami | Userland Programming & Scripting | 23 | May 5th, 2010 17:07 |
| [Solved] Exporting env vars to other xterms | sim | General | 3 | November 14th, 2009 04:25 |