On Mon, Feb 1, 2016 at 6:28 PM, Justin Garrison wrote:
> /bin/kill -RTMIN+22 1
>> systemctl islolate ...
>> journalctl -b
>
>
> -RTMIN+22 doesn't appear to be a valid kill flag and I couldn't find
> documentation on which flags do what for systemd
>
The signals are documented in `man systemd`.
>
> /bin/kill -RTMIN+22 1
> systemctl islolate ...
> journalctl -b
-RTMIN+22 doesn't appear to be a valid kill flag and I couldn't find
documentation on which flags do what for systemd
I tried -RTMIN+2 and the system hung and told me it was going to shut down
but didn't. I switched ttys and tried
Hi,
I faced a question about the behavior when both TimeoutSec and TimeoutStartSec
or TimeoutStopSec are defined in the same .service file.
I could hardly find any hints in the man page and could only confirm the
behavior by reading the code.
Afterwards I found a discussion about this behavior
On Mon, Feb 1, 2016 at 11:54 AM, arnaud gaboury
wrote:
> On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas
> wrote:
> > On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury <
> [email protected]>
> > wrote:
> >>
> >> $ systemctl --version
> >> systemd 22
> >
> >
> > v22 was released five years
Am 01.02.2016 um 10:54 schrieb arnaud gaboury:
On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas wrote:
Search systemd.unit(5) for "drop-in". There is no special syntax, the
additional .conf files act exactly like a part of the main unit file.
Yes I have seen it. This mechanism uses
/etc/sy
On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas wrote:
> On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury
> wrote:
>>
>> $ systemctl --version
>> systemd 22
>
>
> v22 was released five years ago, are you sure?
222, sorry for the typo
>
>>
>> One way to pass additional options is to add one of
On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury
wrote:
> $ systemctl --version
> systemd 22
>
v22 was released five years ago, are you sure?
> One way to pass additional options is to add one of these lines in
> the [Service] part of the unit file:
>
>
> Environment=ONE='one'
> E
$ systemctl --version
systemd 22
One way to pass additional options is to add one of these lines in
the [Service] part of the unit file:
Environment=ONE='one'
EnvironmentFile=/path/to
---
If I am right, there is another possible mechanism since recent
versions by ad
