I've tried getting this to work with no luck. It seems that
VCL never closes the log file and there doesn't look to be any
way to do so without restarting VCL. The big question then is:
when is it safe to restart VCLd?
Most programs use SIGHUP to reread-config files, and also
reset log files. VCLd does not do this, since HUNTSMAN() is
linked to $SIG{HUP} and that effectively ends VCLd.
What would be a good way to reset the log files in both VCLd
and any forked children?
If I can come up with a way to do this, would the VCL project
be interested in a patch?
- Cliff
