On 03/05/17 21:29, Michael Biebl wrote:
>
> Keep in mind, that in most cases you don't need to override the package
> provided service file completely by making a full copy of it in
> /etc/systemd/system
>
> You can extend/override individual bits via drop-in files (e.g. adding
> additional depen
Hi.
On Mon, 6 Mar 2017 14:25:44 +
Jonathan Dowland wrote:
> On Tue, Feb 28, 2017 at 10:25:52AM -0500, Marc Auslander wrote:
> > IIRC in the "old" world, if you had a modified version of a config
> > file and an update modified the original released version, you got
> > a warning and
On Tue, Feb 28, 2017 at 10:25:52AM -0500, Marc Auslander wrote:
> IIRC in the "old" world, if you had a modified version of a config
> file and an update modified the original released version, you got
> a warning and a dialog which let you decide how to proceed.
This is still the case on Debian s
Michael Biebl wrote:
> Useful in that regard is also systemd-delta, which will show you local
> overrides or extensions.
Which still does not work for instanced units.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797839 and
https://github.com/systemd/systemd/issues/45
Grüße,
S°
--
Sigme
Am 05.03.2017 um 21:29 schrieb Michael Biebl:
> Fwiw, systemctl edit (--full) foo.service can help you with that
>
> https://www.freedesktop.org/software/systemd/man/systemctl.html#edit%20NAME%E2%80%A6
>
> This is new in stretch, jessie's systemctl doesn't have that yet.
Just to clarify here: Th
Am 05.03.2017 um 20:47 schrieb Harald Dunkel:
> On 02/28/17 15:23, Dominique Dumont wrote:
>
>> I don't understand why a change in /lib/systemd/system should trigger a
>> conflict warning.
>
>
> A unit file provided by the package maintainer might introduce new
> dependencies, for example. Mayb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/28/17 15:23, Dominique Dumont wrote:
>
> I don't understand why a change in /lib/systemd/system should trigger a
> conflict warning.
>
A unit file provided by the package maintainer might introduce new
dependencies, for example. Maybe an Ex
Marc Auslander wrote:
> Dominique Dumont writes:
>> On Tuesday, 28 February 2017 14:01:18 CET Harald Dunkel wrote:
>>> short question about /lib/systemd/system: AFAICS the config
>>> files here are supposed to be overridden by local config files
>>> in /etc/systemd/system, using the same path, as
Dominique Dumont writes:
> On Tuesday, 28 February 2017 14:01:18 CET Harald Dunkel wrote:
>> short question about /lib/systemd/system: AFAICS the config
>> files here are supposed to be overridden by local config files
>> in /etc/systemd/system, using the same path, as described in
>> systemd.uni
On Tuesday, 28 February 2017 14:01:18 CET Harald Dunkel wrote:
> short question about /lib/systemd/system: AFAICS the config
> files here are supposed to be overridden by local config files
> in /etc/systemd/system, using the same path, as described in
> systemd.unit(5)
>
> How can I make sure tha
Hi folks,
short question about /lib/systemd/system: AFAICS the config
files here are supposed to be overridden by local config files
in /etc/systemd/system, using the same path, as described in
systemd.unit(5)
How can I make sure that there is a conflict dialog at upgrade
time, if I have to modif
11 matches
Mail list logo
