From: Carl W. S. <ch...@re...> - 2006-02-14 18:16:38
|
On 02/14 11:41 , Les Mikesell wrote: > I have to disagree on this one, although in a pure-perl app it > doesn't matter a lot and with a cgi interface you need to know > what executes every hit and what doesn't. MimeDefang is a great > example of where the config file being a snippet of perl allows > the local admin to easily do things no one else had even considered, > something that's impossible if all you can do is set some canned > variables. I accept this. I understand that the flexibility offered is worthwhile. My problem is config files that are like wet noodles... so flexible that they're hard to pick up. :) > It doesn't have to be confusing. I'd rephrase your comment above > and say that just because it can be confusing doesn't mean it > should be. fair enough. Hypothetically speaking, maybe the solution (not necessarily for BackupPC, just an abstract comment here) is to have two levels of config files... one intended to hold the fancy scripting stuff, and the other being an idiot-level name=value tuple file that's easy to understand. perhaps that's too complex tho, and I can see how if handled improperly, can make the situation worse. (witness LogWatch). > > b. it's immediately discouraging to those of us who can't > > Learning perl will save time for a system administrator. But > you should only need to know it to do things that would otherwise > not be possible at all. there is definitely value in it; and once upon a time I knew some of it. I haven't needed it recently, so I've lost what knowlege I once had. I've generally found bash scripts to be adequate for my needs; YMMV. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com |