On 02/13 07:34 , Craig Barratt wrote: > Putting perl code in the config file has some drawbacks. First, it won't > work with the new config editor (but that's not released yet). Second, > any code that takes time to execute (eg: contacting a client to list its > modules) will make the CGI script run slowly since it is read on every > request specific to that client.
thank God you're sensible about this, Craig. Entirely too many perl mongers have the idea that just because one can put perl script into a config file, that it should be done. (Witness the abominable config files for LogWatch). Other reasons to avoid scripts in config files: a. it makes the config confusing to read, even for those people who can write perl b. it's immediately discouraging to those of us who can't Thanks again for a sensibly and cleanly designed tool, Craig. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/