Good day,
I've recently deployed systemd on a machine that uses some syslog
monitoring software and the software went nuts because messages from
systemd logger were inconsistent with other logging - they all look
like this:
kernel.warning kernel[-]: process[pid]: message contents
Thus, regard
On Tue, 22 Feb 2011 14:37:41 +0100
Lennart Poettering wrote:
> On Tue, 22.02.11 12:33, Cristian Patrascu (cristian.patra...@windriver.com)
> wrote:
>
...
>
> I'd be happy to merge a patch that adds native switches to systemd for
> the most relevant cgroup settings of the various hierarchies. Fo
On Tue, 22.02.11 12:33, Cristian Patrascu (cristian.patra...@windriver.com)
wrote:
> Hi!
>
> I have some questions regarding the options in a .service that can
> limit the resources of an application specified in ExecStart:
> 1. For memory resource I know there is the "LimitAS" option, but
> wha
On 02/22/2011 11:33 AM, Cristian Patrascu wrote:
> 2. If there is such an option, is there a way to read the specified cpu
> limit from the control group hierarchy?
If you put a cpu.share value in the cpu cgroup, all processes in that
group have a weight of that value. read the cgroup docs how th
systemd+udev can't replace rc.sysinit(or external script like
fedora-storage-init) now. :(
>>>
>>> For the second case, can you see if this patch:
>>>
>>> http://article.gmane.org/gmane.linux.lvm.devel/6138
>>>
>>> helps for you?
>> Ok, I will test this. Thank you.
>>>
>>> It replaces the
Hi!
I have some questions regarding the options in a .service that can limit
the resources of an application specified in ExecStart:
1. For memory resource I know there is the "LimitAS" option, but what
about limiting the CPU, is there any option? For CPU limiting I'm
interested in specifying
