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
On Tue, 2006-02-14 at 08:29, Carl Wilhelm Soderstrom 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)
Les Mikesell wrote:
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).
I have to disagree on this one, although
[EMAIL PROTECTED] writes:
As you can see, this is going pretty slow on my side, but I'll keep making
progress from time to time.
I tried to do the easiest thing first, i.e., switching to using rsyncd,
instead of rsync, and hardcoding the rsyncd modules in the config file for
a particular
