Am 08.03.2013 06:31, schrieb Holger Winkelmann:
- Original Message -
Hey!
Finally, here's 198, with many big changes:
* Resource limits (as exposed by the various control group
controllers) can now be controlled dynamically at runtime
for all units.
HI,
* Resource limits (as exposed by the various control group
controllers) can now be controlled dynamically at runtime
for all units. More specifically, you can now use a command
like systemctl set-cgroup-attr foobar.service cpu.shares
The documentation makes it sound like ExecStopPost is only run when
stopping the service with `systemctl stop foo.service`
However, that is not the case, as it also gets run when the service
unexpectedly exists, crashes, or gets SIGKILLed.
---
man/systemd.service.xml | 4 ++--
1 file changed, 2
On Fri, Mar 08, 2013 at 10:26:38AM +0100, Holger Winkelmann wrote:
HI,
* Resource limits (as exposed by the various control group
controllers) can now be controlled dynamically at runtime
for all units. More specifically, you can now use a command
Hi,
Thanks for the quick look. Thats What I thought anyway by reading the
announcement.
which means deleting the directories will bring the system in the sate the
service
unit author or the admin intended, sweet...
Let see where this concept evolves in terms of general settings for a
From: Harald Hoyer har...@redhat.com
---
src/cryptsetup/cryptsetup-generator.c | 209 +++---
1 file changed, 65 insertions(+), 144 deletions(-)
diff --git a/src/cryptsetup/cryptsetup-generator.c
b/src/cryptsetup/cryptsetup-generator.c
index 38a7cfa..0a51db8 100644
Hi,
Sorry for troubling you, but I have got an issue to confirm with you.
My issue is when I use the following command:
systemd-cat --priority=0 echo hello
Nothing logged into the journal, and the exit code is 141. I wonder
whether it is
a bug or it just work as expected.
My system is
Dne 8.3.2013 10:57, Yan Lei napsal(a):
Sorry for troubling you, but I have got an issue to confirm with you.
My issue is when I use the following command:
systemd-cat --priority=0 echo hello
Nothing logged into the journal, and the exit code is 141. I wonder
whether it is
a bug or it
Hi,
What would be the advantage of placing an early boot up script in between
local-fs.target/sysinit.target OR in between sysinit.target/basic.target?
I cannot decide what should be the ordering for some early initialization
oneshot services I have in my embedded system. These services makes
Am 08.03.2013 14:12, schrieb Umut Tezduyar:
To summarize, where are users encouraged to place their early boot up
initialization services (ex: setting up the
bandwith on a NIC)?
[root@rh:~]$ systemctl status bandwidth.service
bandwidth.service - Traffic-Shaping
Loaded: loaded
Maybe bandwith wasn't the best example :) But my question is still valid.
On Fri, Mar 8, 2013 at 2:18 PM, Reindl Harald h.rei...@thelounge.netwrote:
Am 08.03.2013 14:12, schrieb Umut Tezduyar:
To summarize, where are users encouraged to place their early boot up
initialization services
Hi,
I have realized that return of systemctl isolate target command is only
synchronous for starting jobs but not for stopping jobs. How can one
make sure when systemctl isolate target returns, services that are
needed to be stopped are stopped AND services that are needed to be started
are
On Fri, Mar 08, 2013 at 04:26:36AM -0500, Mathieu Bridon wrote:
The documentation makes it sound like ExecStopPost is only run when
stopping the service with `systemctl stop foo.service`
However, that is not the case, as it also gets run when the service
unexpectedly exists, crashes, or gets
On Fri, 08.03.13 06:31, Holger Winkelmann (h...@travelping.com) wrote:
Hi,
Nice to see that... seems it was time for a release... ;-)
a few questions in line:
- Original Message -
Hey!
Finally, here's 198, with many big changes:
* Resource limits (as
On Fri, 08.03.13 10:39, Tomasz Torcz (to...@pipebreaker.pl) wrote:
On Fri, Mar 08, 2013 at 10:26:38AM +0100, Holger Winkelmann wrote:
HI,
* Resource limits (as exposed by the various control group
controllers) can now be controlled dynamically at runtime
On Fri, 08.03.13 10:47, Holger Winkelmann (h...@travelping.com) wrote:
Hi,
Thanks for the quick look. Thats What I thought anyway by reading the
announcement.
which means deleting the directories will bring the system in the sate the
service
unit author or the admin intended, sweet...
We should not try to get information about mount unit from fragment
if the unit was created because of /proc/self/mountinfo event.
---
src/core/mount.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/core/mount.c b/src/core/mount.c
index 419cf27..df9 100644
---
Hi everyone,
I haven't tested the patch, so suggestions and testing are very appreciated.
Regards,
Michal
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Friday, March 08, 2013 09:40 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Mar 08, 2013 at 04:26:36AM -0500, Mathieu Bridon wrote:
The documentation makes it sound like ExecStopPost is only run when
stopping the service with `systemctl stop foo.service`
However, that is not the case, as it
Hi,
I thought mounts coming from mountinfo are not getting default dependencies
anyways. mount_add_one() never sets load_extras to true for new mount
units. load_extras is the control to call mount_add_extras which will
eventually call mount_add_default_dependencies(). Or I have replied to
On 03/08/2013 03:13 PM, Michal Sekletar wrote:
@@ -447,7 +447,11 @@ static int mount_add_default_dependencies(Mount *m) {
if (UNIT(m)-manager-running_as != SYSTEMD_SYSTEM)
return 0;
-p = get_mount_parameters_fragment(m);
+if (m-from_fragment)
+
On Fri, Mar 08, 2013 at 03:09:21AM +0100, Michael Biebl wrote:
2013/3/8 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
Hi,
Michael Biebl pointed out that some links in
www.freedesktop.org/software/systemd/man/index.html are
broken. Unfortunately all links to man page aliases are broken.
On 03/08/2013 03:25 PM, Umut Tezduyar wrote:
I thought mounts coming from mountinfo are not getting default
dependencies anyways. mount_add_one() never sets load_extras to true
for new mount units.
But it does call unit_add_to_load_queue(u), which should eventually
result in mount_load()
In fact, the drop-in logic I added primarily to have a nice place
where set-cgroup-attr could be made persistent.
Maybe it's better to have generic interface for setting parameters,
instead of this specific one?
___
systemd-devel mailing list
On Fri, 08.03.13 16:53, Oleksii Shevchuk (alx...@gmail.com) wrote:
In fact, the drop-in logic I added primarily to have a nice place
where set-cgroup-attr could be made persistent.
Maybe it's better to have generic interface for setting parameters,
instead of this specific one?
The
From: Harald Hoyer har...@redhat.com
Now works as expected for me.
$ mount 192.168.2.2:/Public /mnt/test
$ systemctl status mnt-test.mount
mnt-test.mount - /mnt/test
Loaded: loaded (/proc/self/mountinfo)
Active: active (mounted) since Fr 2013-03-08 16:24:38 CET; 11s ago
Lennart, thanks for answer, but probably I mean something else.
set-cgroup-attr creates drop-in with ControlGroupAttribute= for unit. Why don't
have something like
systemctl set unit.service ControlGroupAttribute=cpu.shared 2000
systemctl set unit.service ConditionPathExists=/run/blah
and so
From: Harald Hoyer har...@redhat.com
Now works as expected for me.
$ mount 192.168.2.2:/Public /mnt/test
$ systemctl status mnt-test.mount
mnt-test.mount - /mnt/test
Loaded: loaded (/proc/self/mountinfo)
Active: active (mounted) since Fr 2013-03-08 16:24:38 CET; 11s ago
Am 08.03.2013 15:49, schrieb Michal Schmidt:
On 03/08/2013 03:25 PM, Umut Tezduyar wrote:
I thought mounts coming from mountinfo are not getting default
dependencies anyways. mount_add_one() never sets load_extras to true
for new mount units.
But it does call unit_add_to_load_queue(u),
From: Harald Hoyer har...@redhat.com
Now works as expected for me.
$ mount 192.168.2.2:/Public /mnt/test
$ systemctl status mnt-test.mount
mnt-test.mount - /mnt/test
Loaded: loaded (/proc/self/mountinfo)
Active: active (mounted) since Fr 2013-03-08 16:24:38 CET; 11s ago
From: Harald Hoyer har...@redhat.com
Now works as expected for me.
$ mount 192.168.2.2:/Public /mnt/test
$ systemctl status mnt-test.mount
mnt-test.mount - /mnt/test
Loaded: loaded (/proc/self/mountinfo)
Active: active (mounted) since Fr 2013-03-08 16:24:38 CET; 11s ago
From: Harald Hoyer har...@redhat.com
Now works as expected for me.
$ mount 192.168.2.2:/Public /mnt/test
$ systemctl status mnt-test.mount
mnt-test.mount - /mnt/test
Loaded: loaded (/proc/self/mountinfo)
Active: active (mounted) since Fr 2013-03-08 16:24:38 CET; 11s ago
32 matches
Mail list logo
