Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

[Jonathan Dowland]

On Mon, Sep 26, 2016 at 12:31:10PM +0200, Reindl Harald wrote:
> because earlier systems (sysvinit) hat no concept like emergency mode as
> they where a lousy bunch of scripts where you ended in case of a crucial
> disk failing in a undefined state?
> 
> because earlier systems had no concept for "nofail" or "fail" at all

At least on Debian, nofail was honoured and did have an effect, prior to
adopting systemd.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] assign variable to some service item

[Brian Kroth]

I asked about something similar to this a while back. I think the answer
was that variable expansion only works in the Exec* directives.

Cheers,
Brian

On Thu, Sep 29, 2016, 03:26 Vasiliy Tolstov  wrote:

> I have CPUAffinity inside service file and want to configure it via
> EnvironmentFile, but
> CPUAffinity=$CPUAffinity does not work with message Failed to parse
> CPU affinity '$CPUAffinity'
> Environment file contains CPUAffinity="0-2"
> Does it possible to assign cpu affinity via env variable ?
> Thanks!
>
>
> --
> Vasiliy Tolstov,
> e-mail: v.tols...@selfip.ru
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] mysql open_files_limit controlled by systemd

[Hajo Locke]

Hello,

Am 29.09.2016 um 12:05 schrieb Reindl Harald:



Am 29.09.2016 um 11:56 schrieb Hajo Locke:

Hello,

Am 29.09.2016 um 11:30 schrieb Tomasz Torcz:

On Thu, Sep 29, 2016 at 11:20:34AM +0200, Hajo Locke wrote:

Hello List,

we found out that mysql open_files_limit ist controlled by
systemd-service
file. We used LimitNOFILE to increase default value.
This value is always overwriting the value from my.cnf file.
Is there a way to tell systemd to not control a service in this way so
control completely goes back to original my.cnf values?
At the moment i did not found a promising directive.

   Set LimitNOFILE=infinity.  Then your MySL may set the limit
on it own, to the value from my.cnf.


Unfortunately this is not working. We set value in my.cnf lesser than
value in mysql.service, but its only the value in mysql.service which
rules.
May be an OS specific setting? We use Ubuntu 16.04.
It would be nice to tell systemd to let some services make their own 
rules


to gain what?

/etc/systemd/system/mysqld.service.d/ is *exactly* there to override 
values machine specific and so there is no single reason to keep that 
stuff in "my.cnf" as well as there is no reason to use mysqld_safe in 
a systemd environemnt and all proper configured mysql/mariadb servers 
using systemd capabilities where not affected from the shortly 
announced root-exploit


it's a broken design that a application itself controls os ressources

thanks, for your help. this is answering some questions.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Thanks,
Hajo
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] mysql open_files_limit controlled by systemd

[Reindl Harald]

Am 29.09.2016 um 11:56 schrieb Hajo Locke:

Hello,

Am 29.09.2016 um 11:30 schrieb Tomasz Torcz:

On Thu, Sep 29, 2016 at 11:20:34AM +0200, Hajo Locke wrote:

Hello List,

we found out that mysql open_files_limit ist controlled by
systemd-service
file. We used LimitNOFILE to increase default value.
This value is always overwriting the value from my.cnf file.
Is there a way to tell systemd to not control a service in this way so
control completely goes back to original my.cnf values?
At the moment i did not found a promising directive.

   Set LimitNOFILE=infinity.  Then your MySL may set the limit
on it own, to the value from my.cnf.


Unfortunately this is not working. We set value in my.cnf lesser than
value in mysql.service, but its only the value in mysql.service which
rules.
May be an OS specific setting? We use Ubuntu 16.04.
It would be nice to tell systemd to let some services make their own rules


to gain what?

/etc/systemd/system/mysqld.service.d/ is *exactly* there to override 
values machine specific and so there is no single reason to keep that 
stuff in "my.cnf" as well as there is no reason to use mysqld_safe in a 
systemd environemnt and all proper configured mysql/mariadb servers 
using systemd capabilities where not affected from the shortly announced 
root-exploit


it's a broken design that a application itself controls os ressources
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] mysql open_files_limit controlled by systemd

[Tomasz Torcz]

On Thu, Sep 29, 2016 at 11:20:34AM +0200, Hajo Locke wrote:
> Hello List,
> 
> we found out that mysql open_files_limit ist controlled by systemd-service
> file. We used LimitNOFILE to increase default value.
> This value is always overwriting the value from my.cnf file.
> Is there a way to tell systemd to not control a service in this way so
> control completely goes back to original my.cnf values?
> At the moment i did not found a promising directive.

  Set LimitNOFILE=infinity.  Then your MySL may set the limit
on it own, to the value from my.cnf.


-- 
Tomasz Torcz   72->|   80->|
xmpp: zdzich...@chrome.pl  72->|   80->|

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] mysql open_files_limit controlled by systemd

[Hajo Locke]

Hello List,

we found out that mysql open_files_limit ist controlled by 
systemd-service file. We used LimitNOFILE to increase default value.

This value is always overwriting the value from my.cnf file.
Is there a way to tell systemd to not control a service in this way so 
control completely goes back to original my.cnf values?

At the moment i did not found a promising directive.

Thanks,
Hajo
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] assign variable to some service item

[Vasiliy Tolstov]

I have CPUAffinity inside service file and want to configure it via
EnvironmentFile, but
CPUAffinity=$CPUAffinity does not work with message Failed to parse
CPU affinity '$CPUAffinity'
Environment file contains CPUAffinity="0-2"
Does it possible to assign cpu affinity via env variable ?
Thanks!


-- 
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel