Am 07.05.21 um 02:12 schrieb Michael Biebl:
exim4 is unfortunately still SysV-only and doesn't ship a native systemd
.service file. So the correct command is
"update-rc.d exim4 disable"
For the curious: you can run "systemctl disable exim4" as well.
This will just run the above command though
exim4 is unfortunately still SysV-only and doesn't ship a native systemd
.service file. So the correct command is
"update-rc.d exim4 disable"
"update-rc.d exim4 remove" will remove the symlinks in /etc/rc?.d/ but on
the next package update, they will be recreated.
So if you want to make this a
On Wed, May 05, 2021 at 05:27:13PM +0300, Andrei POPESCU wrote:
> On Mi, 05 mai 21, 07:46:03, Greg Wooledge wrote:
> >
> > You're using a package that has not yet been converted to systemd. It's
> > still using an old init.d script, and systemd is performing a conversion
> > on the fly.
> >
> >
On Mi, 05 mai 21, 07:46:03, Greg Wooledge wrote:
>
> You're using a package that has not yet been converted to systemd. It's
> still using an old init.d script, and systemd is performing a conversion
> on the fly.
>
> The basic start and stop subcommands will work fine, but disable may
> not
On Wed, May 05, 2021 at 12:07:29PM +0100, Joe wrote:
> On Tue, 4 May 2021 18:44:12 -0400
> Greg Wooledge wrote:
> >
> > Could you kindly tell us what "systemctl status exim4.service" says
> > on this buster machine of yours? Perhaps your command is turning up
> > one of the automatically
On Tue, 4 May 2021 18:44:12 -0400
Greg Wooledge wrote:
> On Tue, May 04, 2021 at 10:14:45PM +0100, Joe wrote:
> > ...and buster. It's exim4.service as stated by:
> > systemctl --type=service | grep exim
>
> According to packages.debian.org[1] there is no such file in any
> package.
>
> Of
On Tue, May 04, 2021 at 10:14:45PM +0100, Joe wrote:
> ...and buster. It's exim4.service as stated by:
> systemctl --type=service | grep exim
According to packages.debian.org[1] there is no such file in any
package.
Of course, that's not proof of the nonexistence of such a file, because
it
On Tue, 4 May 2021 18:27:57 +0100
Joe wrote:
> On Tue, 4 May 2021 13:15:51 -0400
> Greg Wooledge wrote:
>
> > On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> > > That was the question, Greg:
> > >
> > > "Searching for exim in
> > >
On Tue, May 04, 2021 at 01:46:29PM -0700, John Conover wrote:
>
> Try:
>
> man update-rc.d
> man 8 update-rc.d
>
Please stop top-posting, and please reply to the list.
> Greg Wooledge writes:
> > On Tue, May 04, 2021 at 01:27:56PM -0700, John Conover wrote:
> > > As per the man page
On Tue, May 04, 2021 at 01:27:56PM -0700, John Conover wrote:
> As per the man page for System V init, to disable launching of exim:
>
> update-rc.d -f exim remove
What man page is this allegedly from, exactly?
For the archives, this issue was created by looking for penetration
vulnerabilities during the boot of a Debian Buster machine using
tcpdump(1) on a machine between Buster, and the it's Internet facing
router.
There was exim traffic when exim boots, but exim was SUPPOSED to be
disabled during
On 5/4/2021 7:28 PM, Erwan David wrote:
Le 04/05/2021 à 19:26, Joe a écrit :
On Tue, 4 May 2021 10:03:43 -0700
cono...@rahul.net (John Conover) wrote:
Greg Wooledge writes:
On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
Searching for exim in
On Tue, May 04, 2021 at 10:27:17AM -0700, John Conover wrote:
>
> Thanks, Greg. "update-rc.d -f exim remove" is the command for
> /etc/init.d. But its broken.
You forgot to reply to the list.
Nobody with any sense uses update-rc.d for system admin work. It's
there for Debian packages to use,
Le 04/05/2021 à 19:26, Joe a écrit :
> On Tue, 4 May 2021 10:03:43 -0700
> cono...@rahul.net (John Conover) wrote:
>
>> Greg Wooledge writes:
>>> On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
Searching for exim in
/etc/systemd/system/multi-user.target.wants/* and
On Tue, 4 May 2021 13:15:51 -0400
Greg Wooledge wrote:
> On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> > That was the question, Greg:
> >
> > "Searching for exim in
> > /etc/systemd/system/multi-user.target.wants/* and
> > /lib/systemd/system/* yields nothing."
> >
On Tue, 4 May 2021 10:03:43 -0700
cono...@rahul.net (John Conover) wrote:
> Greg Wooledge writes:
> > On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> > > Searching for exim in
> > > /etc/systemd/system/multi-user.target.wants/* and
> > > /lib/systemd/system/* yields nothing.
> >
On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> That was the question, Greg:
>
> "Searching for exim in
> /etc/systemd/system/multi-user.target.wants/* and
> /lib/systemd/system/* yields nothing."
>
> so, it wasn't there. Which service?, (or how to find out?)
So... I
Greg Wooledge writes:
> On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> > Searching for exim in /etc/systemd/system/multi-user.target.wants/*
> > and /lib/systemd/system/* yields nothing.
> >
> > How do I stop exim from launching across boots?
>
> Presumably there is a systemd
On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> Searching for exim in /etc/systemd/system/multi-user.target.wants/*
> and /lib/systemd/system/* yields nothing.
>
> How do I stop exim from launching across boots?
Presumably there is a systemd service, which is enabled. You will
I use either exim or another MTA. When I want to use the other MTA,
"update-rc.d -f exim remove" does not remove exim from "ps eax" after
today's exim update.
Searching for exim in /etc/systemd/system/multi-user.target.wants/*
and /lib/systemd/system/* yields nothing.
How do I stop exim from
20 matches
Mail list logo
