Am 27.03.2014 13:26, schrieb Gesh:
> But what if bar.unit Wants=foo.unit and I add a custom foo.unit to
> bar.unit.wants/ ? Will both be run? Will the custom foo.unit replace the
> built-in?
I don't know what happens if you try, but there can only be one unit of
the same name.
signature.asc
On March 27, 2014 11:20:04 AM GMT+02:00, "Thomas Bächler"
wrote:
>Am 27.03.2014 09:41, schrieb Gesh:
>> Basically, if I understood what happens correctly, the units under
>/etc/systemd/system/*.wants/ - or their targets, if they're symlinks -
>replace their corresponding units in the dependency g
Am 27.03.2014 09:41, schrieb Gesh:
> Basically, if I understood what happens correctly, the units under
> /etc/systemd/system/*.wants/ - or their targets, if they're symlinks -
> replace their corresponding units in the dependency graph.
Not exactly.
When you place a unit in foo.wants, then foo
On March 27, 2014 9:25:24 AM GMT+02:00, "Thomas Bächler"
wrote:
>Am 26.03.2014 23:13, schrieb Gesh:
>> Thanks for the pointers.
>> If I understand what's going on correctly, units specify in their
>[Install] section whether, when they're enabled, they should be pulled
>in by other units.
>> Those
Am 26.03.2014 23:13, schrieb Gesh:
> Thanks for the pointers.
> If I understand what's going on correctly, units specify in their [Install]
> section whether, when they're enabled, they should be pulled in by other
> units.
> Those symlinks usually populate the appropriate directory under
> /etc
Am 19.03.2014 20:16, schrieb Ary Kleinerman:
>> There's not really much magic going on. Are you aware of:
>>
>> /etc/systemd/system
>>
>> This contains symlinks that do already pretty much what you describe, and
>> this
>> is systemd's native configuration.
>>
> Paul,
> Don't forget
> /run/systemd
On Thu, Mar 27, 2014 at 12:13:08AM +0200, Gesh wrote:
> On March 19, 2014 9:16:57 PM GMT+02:00, Ary Kleinerman
> wrote:
> >> There's not really much magic going on. Are you aware of:
> >>
> >> /etc/systemd/system
> >>
> >> This contains symlinks that do already pretty much what you describe,
> >a
That is correct, when you call `systemctl enable foo.unit` then the
[Install] section of the unit file is "executed". "Static" means that
the unit has no [Install] section, meaning it is permanently
enabled/disabled as far as the systemctl enable/disable tool is
concerned. Other than pulling themse
On March 19, 2014 9:16:57 PM GMT+02:00, Ary Kleinerman
wrote:
>> There's not really much magic going on. Are you aware of:
>>
>> /etc/systemd/system
>>
>> This contains symlinks that do already pretty much what you describe,
>and this
>> is systemd's native configuration.
>>
>Paul,
>Don't forget
> There's not really much magic going on. Are you aware of:
>
> /etc/systemd/system
>
> This contains symlinks that do already pretty much what you describe, and this
> is systemd's native configuration.
>
Paul,
Don't forget
/run/systemd/system: Runtime units and /usr/lib/systemd/system: Units
of i
On Wednesday 19 Mar 2014 12:52:55 Gesh wrote:
> Dear all,
> I've been rereading the old arguments on the rc.conf split.
> Disregarding everything discussed there, one interesting
> point came up during that discussion.[1]
> Is it possible to have some configuration file, e.g.
> /etc/systems/service
11 matches
Mail list logo
