On Fri, 2016-02-12 at 15:06 +, RW wrote:
> On Thu, 11 Feb 2016 21:05:26 +
> Martin Gregorie wrote:
>
> > Feb 7 00:29:22 zoogz spamd[9347]: spamd: server killed by SIGTERM,
> > shutting down
> > Feb 7 00:29:22 zoogz spamd[9347]: spamd: cannot send SIGINT to
> > child
> > process [9352]: N
On Thu, 11 Feb 2016 21:05:26 +
Martin Gregorie wrote:
> On Thu, 2016-02-11 at 19:09 +, RW wrote:
> > On Thu, 11 Feb 2016 12:02:13 +
> > Martin Gregorie wrote:
> >
> > > Every so often I see the following in my nightly logwatch rep
> > >
>
On Thu, 2016-02-11 at 19:09 +, RW wrote:
> On Thu, 11 Feb 2016 12:02:13 +
> Martin Gregorie wrote:
>
> > Every so often I see the following in my nightly logwatch rep
> >
> > Child-related errors
> > spamd: cannot send SIGINT to child process [___]:
On Thu, 11 Feb 2016 12:02:13 +
Martin Gregorie wrote:
> Every so often I see the following in my nightly logwatch report:
>
> Child-related errors
> spamd: cannot send SIGINT to child process [___]: No such process:
> 1 Time(s)
>
Is it literally "[___]" in the log?
Every so often I see the following in my nightly logwatch report:
Child-related errors
spamd: cannot send SIGINT to child process [___]: No such process:
1 Time(s)
On at least one occasion it seems to be related to systemd deciding its
time to restart my mailing system because systemd is
