I have systemd service, say foo.service.
*Service file*
[Unit]
Description=Foo agent.
After=fooAfter.service
Before=fooBefore1.service
Before=fooBefore2.service
[Service]
# During boot the foo.sh script reads input from /dev/console. If the
user
# hits , it will skip waiting for
HI all,
We’re seeing the following warning upon reboot of our machines: octeon_wdt: WDT
device closed unexpectedly
I believe it’s caused from the following code block in src/core/main.c:
if (arm_reboot_watchdog && arg_shutdown_watchdog > 0) {
char *e;
/* If we reboo
Am 14.01.2016 um 21:44 schrieb Lennart Poettering:
On Thu, 14.01.16 19:52, Reindl Harald ([email protected]) wrote:
Am 14.01.2016 um 15:58 schrieb Lennart Poettering:
And no, unit files are not supposed to be a templating language and do
not support generlized variable expansion and qui
On Thu, 14.01.16 20:37, Tom H ([email protected]) wrote:
> I understand that you'd prefer that we use drop-ins to set
> "Environment=Foo=bar" or override "ExecStart=..." and it probably
> works for most daemons - and should also be non-distro-specific.
>
> But in the case of nfs, it would mean m
On Thu, 14.01.16 19:52, Reindl Harald ([email protected]) wrote:
> Am 14.01.2016 um 15:58 schrieb Lennart Poettering:
> >And no, unit files are not supposed to be a templating language and do
> >not support generlized variable expansion and quite frankly I should
> >never even have added the
On Thu, Jan 14, 2016 at 3:58 PM, Lennart Poettering
wrote:
> On Wed, 13.01.16 10:51, Steve Dickson ([email protected]) wrote:
>>
>> Is is possible to set a variable in the [Unit]
>> section of a service?
>>
>> For example in rpc-gssd.service there is
>> ConditionPathExists=/etc/krb5.keytab
>>
Am 14.01.2016 um 15:58 schrieb Lennart Poettering:
And no, unit files are not supposed to be a templating language and do
not support generlized variable expansion and quite frankly I should
never even have added the limited env var expansion via
EnvironmentFile= that ExecStart= supports, since
> On 01/14/2016 03:01 PM, Lennart Poettering wrote:
>> We currently do not show runtime generated unit files among the output
>> of "systemctl list-unit-files", but it would probably make sense
>
> Aren't these files auto generated on each bootup/reload/restart thus
> exposing them is likely to ca
On 01/14/2016 03:01 PM, Lennart Poettering wrote:
We currently do not show runtime generated unit files among the output
of "systemctl list-unit-files", but it would probably make sense
Aren't these files auto generated on each bootup/reload/restart thus
exposing them is likely to cause conf
Hello!
As an additional idea -- to separate lists of 'systemctl
list-unit-files' command with subkeys --system, --user and --runtime. By
default 'systemctl list-unit-files' should display all unit-files,
including runtime generated ones.
'systemctl list-unit-files --system': to display unit-file
On Wed, 13.01.16 17:26, Stijn De Weirdt ([email protected]) wrote:
> hi all,
>
> i'm having following situation on a centos 7.2 system (systemd-219-19.el7)
>
> there is a sysvinit service called netconsole that is not listed as a
> unit or unitfile, but the unitfile was generated and syste
On Wed, 13.01.16 10:51, Steve Dickson ([email protected]) wrote:
> Hello,
>
> Is is possible to set a variable in the [Unit]
> section of a service?
>
> For example in rpc-gssd.service there is
> ConditionPathExists=/etc/krb5.keytab
>
> but for some installation the krb5.keytab
> is in a di
12 matches
Mail list logo
