On Tue, 02.02.16 11:05, Steve Dickson (ste...@redhat.com) wrote:
> > You can always use some kind of hackery in ExecStartPre, but I don't think
> > that's
> > what anyone wants.
> >
> Well its to bad ConditionPathExists is not part of the [Service] section
> so I could use a shell variable...
On 01/23/2016 11:33 AM, Armin K. wrote:
> On 23.01.2016 17:28, Armin K. wrote:
>>> On 01/13/2016 10:51 AM, Steve Dickson wrote:
Hello,
Is is possible to set a variable in the [Unit]
section of a service?
For example in rpc-gssd.service there is
> On 01/13/2016 10:51 AM, Steve Dickson 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 different
On 23.01.2016 17:28, Armin K. wrote:
>> On 01/13/2016 10:51 AM, Steve Dickson 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
Thank for the discussion... It was very helpful!
steved.
On 01/13/2016 10:51 AM, Steve Dickson 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
On Thu, Jan 14, 2016 at 3:58 PM, Lennart Poettering
wrote:
> On Wed, 13.01.16 10:51, Steve Dickson (ste...@redhat.com) wrote:
>>
>> Is is possible to set a variable in the [Unit]
>> section of a service?
>>
>> For example in rpc-gssd.service there is
>>
Am 14.01.2016 um 21:44 schrieb Lennart Poettering:
On Thu, 14.01.16 19:52, Reindl Harald (h.rei...@thelounge.net) 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
On Thu, 14.01.16 19:52, Reindl Harald (h.rei...@thelounge.net) 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, 14.01.16 20:37, Tom H (tomh0...@gmail.com) 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
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,
On Wed, 13.01.16 10:51, Steve Dickson (ste...@redhat.com) 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
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 different place. The rpc.gssd daemon
can be told this by setting a command line
Am 13.01.2016 um 16:51 schrieb Steve Dickson:
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 different place. The rpc.gssd daemon
can be
13 matches
Mail list logo