Jonathan de Boyne Pollard wrote:
> Sven Hartge:
>> systemd happily runs "legacy" LSB init scripts
>>
> ... except when its one-size-fits-all approach does not work, of
> course. Example:
> * https://unix.stackexchange.com/questions/386846/
> This is
Christian Seiler wrote:
> Now, that doesn't mean that you should still write _new_ init scripts
> for custom services if you're going to use systemd anyway. There it
> will be a good idea to learn how to do that with native systemd
> service units.
Exactly.
I was able to
Am 2017-08-21 11:52, schrieb Tom Browder:
On Mon, Aug 21, 2017 at 02:36 Sven Hartge wrote:
Question: Why do you want to manually replace the init-script from
postfix in Jessie with a systemd.unit? What do you want to
accomplish by
doing so (other than creating a possible
Tom Browder wrote:
> On Mon, Aug 21, 2017 at 02:36 Sven Hartge wrote:
>> Tom Browder wrote:
>>> On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote:
>>> So the question I have is how does it all work? There is
On Mon, Aug 21, 2017 at 02:36 Sven Hartge wrote:
> Tom Browder wrote:
> > On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote:
>
> > So the question I have is how does it all work? There is no init.d,
> > but there seems to be some
Tom Browder wrote:
> On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote:
>> That unit file does effectivly nothing. It just starts "/bin/true" and
>> exits.
>>
>> What it *not* does is starting postfix in any way.
>>
>> This looks like there should be
On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote:
> Tom Browder wrote:
>
> > The contents of the postfix.service file are;
>
...
> That unit file does effectivly nothing. It just starts "/bin/true" and
> exits.
>
> What it *not* does is starting
On Sun, Aug 20, 2017 at 12:30 Sven Hartge wrote:
> Tom Browder wrote:
>
> > The contents of the postfix.service file are;
>
...
>
> That unit file does effectivly nothing. It just starts "/bin/true" and
> exits.
>
> What it *not* does is starting
Tom Browder wrote:
> The contents of the postfix.service file are;
> [Unit]
> Description=Postfix Mail Transport Agent
> Conflicts=sendmail.service exim4.service
> ConditionPathExists=/etc/postfix/main.cf
> [Service]
> Type=oneshot
> RemainAfterExit=yes
>
On Sun, Aug 20, 2017 at 11:41 AM, Nicolas George wrote:
> Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit :
>> So "disabled" is normal?
>
> Indeed. See:
>
>
Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit :
> So "disabled" is normal?
Indeed. See:
https://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/ch-Services_and_Daemons.html#s3-services-configuration-enabling
Regards,
--
Nicolas George
signature.asc
Description: Digital
On Sun, Aug 20, 2017 at 10:17 AM, Nicolas George wrote:
> Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit :
>> > # systemctl start postfix
>> > # systemctl status postfix
>> >
>> > and got several lines basically saying posfix.service was disabled.
>
>> The exact message
On Sun, Aug 20, 2017 at 10:17 Nicolas George wrote:
> Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit :
> > > # systemctl start postfix
> > > # systemctl status postfix
> > >
> > > and got several lines basically saying posfix.service was disabled.
>
> > The exact
Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit :
> > # systemctl start postfix
> > # systemctl status postfix
> >
> > and got several lines basically saying posfix.service was disabled.
> The exact message is:
>
> * postfix.service - Postfix Mail Transport Agent
>Loaded: loaded
Le tridi 3 fructidor, an CCXXV, Tom Browder a écrit :
> I got a postfix.service file from a postfix developer and installed it in
> /etc/systemd/system as the docs mention.
>
> I then moved the /etc/init.d/postfix file away, reloaded the systemd
> daemon, and did:
>
> # systemctl start postfix
On Sun, Aug 20, 2017 at 9:42 AM, Tom Browder wrote:
> I got a postfix.service file from a postfix developer and installed it in
> /etc/systemd/system as the docs mention.
>
> I then moved the /etc/init.d/postfix file away, reloaded the systemd daemon,
> and did:
>
> #
16 matches
Mail list logo