[vps-mail] savelogs - do I misunderstand dry-run

[Marjolein Katsma <tfyj8lv02@xxxxxxxxxxxxxx>]

Scott,

I've now successfully installed savelogs. Made a first configuration file for handling system files (messages and ftp_logs) and tried to run it from the command line, with the extra --dry-run parameter. Nothing. Since the ftp_log wasn't as important for me as messages, I then commented out the line specifying messages, and ran it again from the command line _without_ --dry-run. ftp_log was archived as intended. Then I uncommented te line for messages again, and put the savelogs job in my crontab to run at the start of each month. That worked nicely, too.

Now I've made an additional config for the Apache files. Again, trying to run it from the command line with --dry-run produces no output. Since the new month is only a few hours old, I then ran it from the command line without the --dry-run, and it worked (mostly) as expected.

It looks as though savelogs works fine, but dry-run doesn't, which makes it hard to test a configuration.

Am I misunderstanding what --dry-run should do? I expected some output (stdout) to show me what savelogs _would_ do given the specified configuration file, e.g.,
savelogs --dry-run --conf=etc/sl_apachelogs.conf

savelogs installed (via vinstall savelogs) is version 1.66.



-- 
Marjolein Katsma

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
======================================================================