Klaus Ethgen via Exim-users wrote:
[...]
> did anybody already debug and fix the problem in debian that exim is not
> stopped with stop action anymore?
That is #921205, should be fixed now.
https://salsa.debian.org/exim-team/exim4/commit/7d69adc64e5006ce1d033acbd51681dc8aa3640d
cu Andreas
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Do den 7. Feb 2019 um 8:26 schrieb Jan Ingvoldstad via Exim-users:
> Additionally, as Exim in Debian still uses SYSV init scripts, this would
> probably work better if rewritten to work with systemd, which was
> introduced with Jessie several
On Wed, Feb 06, 2019 at 11:03:34PM +0100, Klaus Ethgen via Exim-users wrote:
> But, and that did change somewhen in the past months, start-stop-daemon
> seems to _not_ stop exim with that anymore. Both definitions above did
> not change for longer times. Just start-stop-daemon did.
>
> I checked,
On 2019-02-06 22:47, Graeme Fowler via Exim-users wrote:
On 6 Feb 2019, at 22:03, Klaus Ethgen via Exim-users
wrote:
So there was a bug introduced in the last few weeks in
start-stop-daemon
that I have to find a way around. The current situation is not
acceptable.
At this point I’m going to
On Wed, Feb 6, 2019 at 11:56 PM Graeme Fowler via Exim-users <
exim-users@exim.org> wrote:
> On 6 Feb 2019, at 22:03, Klaus Ethgen via Exim-users
> wrote:
> > So there was a bug introduced in the last few weeks in start-stop-daemon
> > that I have to find a way around. The current situation is
On 6 Feb 2019, at 22:03, Klaus Ethgen via Exim-users
wrote:
> So there was a bug introduced in the last few weeks in start-stop-daemon
> that I have to find a way around. The current situation is not
> acceptable.
At this point I’m going to be the person who says “this is not an Exim problem”.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mi den 6. Feb 2019 um 10:45 schrieb Evgeniy Berdnikov via Exim-users:
> On Wed, Feb 06, 2019 at 09:47:04AM +0100, Klaus Ethgen via Exim-users wrote:
> > did anybody already debug and fix the problem in debian that exim is not
> > stopped
On 2019-02-06 09:47, Klaus Ethgen wrote:
> did anybody already debug and fix the problem in debian that exim is
> not stopped with stop action anymore?
I run debian on my server but I compile exim from upstream source, so I
had to write my own initscript. I append it below; it seems to work
On 06/02/2019 08:47, Klaus Ethgen via Exim-users wrote:> This is pretty
annoing as logrotate does not stop the daemon
Exim should not care about logfiles being rotated underneath it.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
On Wed, Feb 06, 2019 at 09:47:04AM +0100, Klaus Ethgen via Exim-users wrote:
> Hi Folks,
>
> did anybody already debug and fix the problem in debian that exim is not
> stopped with stop action anymore?
>
> Problem is, that /etc/init.d/exim4 seems to call killproc which calls
> start-stop-daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Folks,
did anybody already debug and fix the problem in debian that exim is not
stopped with stop action anymore?
Problem is, that /etc/init.d/exim4 seems to call killproc which calls
start-stop-daemon to stop the daemon in stop or restart.
11 matches
Mail list logo
