Roger Oberholtzer wrote:

On Wed, Mar 15, 2017 at 10:23 AM, Andreas Mahel wrote:

I added:

Restart=on-failure RestartSec=30

and ran:

systemctl daemon-reload systemctl restart apache2

I guess /usr/lib/systemd/system/apache2.service will be replaced if apache2 is updated?

You could have added a drop-in config file instead. /etc/systemd/system/apache2.service.d/dropin.conf btw, I googled "Fatal Python error: PyEval_SaveThread: NULL tstate" this morning and saw a couple of hits - it might be worth looking up. -- Per Jessen, Zürich (10.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andreas Mahel wrote:

On 15.03.2017 11:46, Per Jessen wrote:

...

Roger Oberholtzer wrote:

...

...

I guess /usr/lib/systemd/system/apache2.service will be replaced if apache2 is updated?

You could have added a drop-in config file instead.

/etc/systemd/system/apache2.service.d/dropin.conf

Cool, thanks for the pointer (once you know the correct naming, googling it gets a lot easier).

Afterwards, "systemctl cat <service>" is very useful to see if your drop-in has been picked up. -- Per Jessen, Zürich (13.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Roger Oberholtzer [03-15-17 10:57]:

On Wed, Mar 15, 2017 at 2:13 PM, Per Jessen wrote:

...

...

...

You could have added a drop-in config file instead.

/etc/systemd/system/apache2.service.d/dropin.conf

There is a link to the file I edited:

/etc/systemd/system/apache.service -> /usr/lib/systemd/system/apache2.service

So, would I remove that link and make the /etc/systemd/system/apache2.service.d/dropin.conf?

Having both seems confusing. And will the link I remove be replaced when the package is updated?

I know. Read the systemd manual...

no, just read the email: "You could have added a drop-in config file instead." restore the edited service file (un-edit), and add the "dropin.conf" file -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Roger Oberholtzer wrote:

Hmm. There currently exists a file with one name in the /etc/systemd/system directory. The suggestion was to add a directory containing a file with a different name. Perhaps the name in the directory just needs to end in .conf.

I think that is correct, yes.

But that still says nothing about the existing file. Remove it?

Nono, certainly not. The drop-in adds or replaces configs in the existing file.

Or, if there is a apache2.service..d directory, is any file then ignored and only the contents of the apache2.service..d directory used?

No, the regular apache service file is used, then amended by whatever you put in the drop in. -- Per Jessen, Zürich (16.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-03-15 16:48, Per Jessen wrote:

Roger Oberholtzer wrote:

...

Hmm. There currently exists a file with one name in the /etc/systemd/system directory. The suggestion was to add a directory containing a file with a different name. Perhaps the name in the directory just needs to end in .conf.

I think that is correct, yes.

...

But that still says nothing about the existing file. Remove it?

Nono, certainly not. The drop-in adds or replaces configs in the existing file.

He has: /etc/systemd/system/apache.service -> /usr/lib/systemd/system/apache2.service I think the one on /etc should be removed. If you edit the file in etc it makes sense to have it, but if both are the same, or a link, you should only have the one in /usr, which should be the original one, not edited. Maybe he edited the one in /usr, and the system retaliated by placing a link in /etc. Thus when there is an update, the one in /usr would be replaced, and perhaps the edited version would remain, the link broken, dunno. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

On 2017-03-16 14:33, Per Jessen wrote:

Carlos E. R. wrote:

...

On 2017-03-15 16:48, Per Jessen wrote:

...

Roger Oberholtzer wrote:

...

Hmm. There currently exists a file with one name in the /etc/systemd/system directory. The suggestion was to add a directory containing a file with a different name. Perhaps the name in the directory just needs to end in .conf.

I think that is correct, yes.

...

But that still says nothing about the existing file. Remove it?

Nono, certainly not. The drop-in adds or replaces configs in the existing file.

He has:

/etc/systemd/system/apache.service -> /usr/lib/systemd/system/apache2.service

I think the one on /etc should be removed. If you edit the file in etc it makes sense to have it, but if both are the same, or a link, you should only have the one in /usr, which should be the original one, not edited.

I think /etc/systemd/system/apache.service is just for convenience, to be able to use 'apache' instead of 'apache2'. You shouldn't edit any of them, link or otherwise, that's the point.

Ah, I didn't notice the absence of the "2". But there is an error here: files in /etc/systemd/system/ are intended to be edited. If this is an exception, the symlink should be /usr/lib/systemd/system/apache.service -> /usr/lib/systemd/system/apache2.service Or be removed completely. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

On 2017-03-16 15:03, Per Jessen wrote:

Carlos E. R. wrote:

...

On 2017-03-16 14:33, Per Jessen wrote:

...

I think /etc/systemd/system/apache.service is just for convenience, to be able to use 'apache' instead of 'apache2'. You shouldn't edit any of them, link or otherwise, that's the point.

Ah, I didn't notice the absence of the "2".

But there is an error here: files in /etc/systemd/system/ are intended to be edited. If this is an exception, the symlink should be /usr/lib/systemd/system/apache.service -> /usr/lib/systemd/system/apache2.service

Maybe - there are a few of them in /etc/systemd/system :

apache.service httpd.service network.service syslog.service.

Alias. Yes. Added by the distribution, not on upstream, I guess. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

On 2017-03-15 14:13, Per Jessen wrote:

Andreas Mahel wrote:

...

On 15.03.2017 11:46, Per Jessen wrote:

...

Roger Oberholtzer wrote:

...

...

I guess /usr/lib/systemd/system/apache2.service will be replaced if apache2 is updated?

You could have added a drop-in config file instead.

/etc/systemd/system/apache2.service.d/dropin.conf

Cool, thanks for the pointer (once you know the correct naming, googling it gets a lot easier).

Afterwards, "systemctl cat <service>" is very useful to see if your drop-in has been picked up.

For my education, what would have that conf file? Just: Restart=on-failure RestartSec=30 and that's all? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

Carlos E. R. wrote:

On 2017-03-15 14:13, Per Jessen wrote:

...

Andreas Mahel wrote:

...

On 15.03.2017 11:46, Per Jessen wrote:

...

Roger Oberholtzer wrote:

...

...

I guess /usr/lib/systemd/system/apache2.service will be replaced if apache2 is updated?

You could have added a drop-in config file instead.

/etc/systemd/system/apache2.service.d/dropin.conf

Cool, thanks for the pointer (once you know the correct naming, googling it gets a lot easier).

Afterwards, "systemctl cat <service>" is very useful to see if your drop-in has been picked up.

For my education, what would have that conf file? Just:

Restart=on-failure RestartSec=30

and that's all?

Yep, that's all. Only the extra config directives you want. -- Per Jessen, Zürich (12.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, Mar 16, 2017 at 1:01 PM, Andreas Mahel wrote:

You would need the section as well:

[Service] Restart=on-failure RestartSec=30

I did have that in the file. I was perhaps too quick to answer the question. Sorry. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org