On 08/19/2014 06:39 AM, Noel Jones wrote:
> It sounds as if you're trying to monitor postfix health.
I find that logwatch(8) does a pretty good job of pointing up running
issues.
On 8/19/2014 8:53 AM, Sascha Hüdepohl wrote:
> Hello!
>
> * Noel Jones (njo...@megan.vbhcs.org) schrieb:
>
>
>> It sounds as if you're trying to monitor postfix health.
>
> No, actually i wanted to check the installation. I'm learning docker and
> am trying to create an image from a Dockerfile.
Hello!
* Noel Jones (njo...@megan.vbhcs.org) schrieb:
> It sounds as if you're trying to monitor postfix health.
No, actually i wanted to check the installation. I'm learning docker and
am trying to create an image from a Dockerfile.
Unfortunately Docker doens't allow set-gid files unless star
On 8/19/2014 4:10 AM, Sascha Hüdepohl wrote:
> Hi!
>
> I would lilke to automatically check if postfix is OK.
>
> So i run postfix check.
It sounds as if you're trying to monitor postfix health.
Unfortunately "postfix check" isn't very useful for that, as it's
designed to test for installation
Hi,
i think i found the problem:
postfix calls postfix-script which uses postlog for output.
from man postlog:
Logging is sent to syslogd(8); when the standard error stream is
connected to a terminal, logging is sent there as well.
Since stderr is no longer the terminal when i use redirect
Hi!
I would lilke to automatically check if postfix is OK.
So i run postfix check.
Example:
# chmod 555 /usr/sbin/postqueue
# postfix check
postfix/postfix-script: warning: not set-gid or not owner+group+world
executable: /usr/sbin/postqueue
Because postfix check doesn't set the exit-code i t
