On Thu, Oct 17, 2013 at 4:54 AM, Andrey Borzenkov arvidj...@gmail.com wrote:
В Thu, 17 Oct 2013 00:07:55 +0200
Kay Sievers k...@vrfy.org пишет:
typically the line looks like this
UUID=b834776d-69d1-49c6-97c1-d6d758a438f0 / ext4 defaults
i doubt that anything smells what none means
It
On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no idea how you end
up with a read-only filesystem.
As a
Am 17.10.2013 14:59, schrieb Warpme:
On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no idea how you end
up with a
On Thu, Oct 17, 2013 at 02:59:37PM +0200, Warpme wrote:
On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no idea how
'Twas brillig, and Warpme at 17/10/13 13:59 did gyre and gimble:
On 10/16/13 9:46 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Oct 16, 2013 at 09:19:43PM +0200, Warpme wrote:
Maybe we should disable [re]mounting / by systemd at all?
All systemd does, is call 'mount -o remount /'. I have no
On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
systemd-remount-fs.service has been run? I've not seen any debug about
it so far on this thread:
systemctl status systemd-remount-fs.service
Col
Col,
Console reports Starting Remount Root and
'Twas brillig, and Warpme at 17/10/13 18:15 did gyre and gimble:
On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
systemd-remount-fs.service has been run? I've not seen any debug about
it so far on this thread:
systemctl status
On 10/17/13 7:59 PM, Colin Guthrie wrote:
'Twas brillig, and Warpme at 17/10/13 18:15 did gyre and gimble:
On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
systemd-remount-fs.service has been run? I've not seen any debug about
it so far on this
'Twas brillig, and Warpme at 17/10/13 20:25 did gyre and gimble:
On 10/17/13 7:59 PM, Colin Guthrie wrote:
'Twas brillig, and Warpme at 17/10/13 18:15 did gyre and gimble:
On 10/17/13 4:27 PM, Colin Guthrie wrote:
Perhaps a dumb question but are you 100% certain that
--- Quick background:
I work with David Strauss @ Pantheon and systemd is a core part of our
platform. Recently we have been running into some scalability issues with
systemd with the time required for `daemon-reload` to complete. We are
seeing situations where this takes a long time (~ 50s) to
On Sun, Oct 13, 2013 at 4:46 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sun, Oct 06, 2013 at 05:20:58AM +0200, Zbigniew Jędrzejewski-Szmek
wrote:
Hi,
sorry for the long delay. I was expecting this review to take
some time, and I was right :)
I started by running
Initial perf results confirm cgroups rework as the culprit. We're
seeing huge time spent in unit_get_members_mask,
cgroup_context_get_mask, and unit_get_cgroup_context.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
12 matches
Mail list logo
