procedural documentation of piler

2020-04-19 Thread sj
Dear piler users, there was a thread on GoBD compliance back in 2017. And the conclusion was that all piler needs is a procedural documentation describing what it does with an email. Finally I've made it, thanks for Adrian to persuading me. https://docs.google.com/document/d

Re: Documentation

2013-03-19 Thread Janos SUTO
On 2013-03-18 23:18, Frank Ellebrecht wrote: There's another thing I just noticed. When running daily-report.php I get »PHP Notice: Undefined variable: usagetrend in /var/piler/www/view/theme/default/templates/health/daily-report.tpl on line 101« there's a typo, and it's $useagetrend in

Re: Documentation

2013-03-18 Thread Janos SUTO
Hello Frank, On 2013-03-18 20:26, Frank Ellebrecht wrote: Just wanted to let you know that I finally succeeded installing the master branch, at least yesterday's build (770). I did have some trouble just post them. I'd like to make the piler install/upgrade as smooth as possible. here

Re: Documentation

2013-03-17 Thread Janos SUTO
Hello, On 2013-03-17 07:40, Frank Ellebrecht wrote: As I had some problems during the installation process, I thought it might be a good idea to share them here and suggest some changes to the documentation: Mandatory packages == The package »sysstat« is required. Without

Re: Documentation

2013-03-17 Thread Frank Ellebrecht
Am Sonntag, den 17.03.2013, 21:13 +0100 schrieb Janos SUTO: Btw, does it make a difference if ClamAV is called by piler or earlier in the delivery process? I assume it's scan results are used for archiving/retention rules, right? There's a difference. If you enable clamav support in