[systemd-devel] mount failed during system start but after systemctl daemon-reload everything works

Hello. Could anyone tell me a reason why a mount (regardless of via fstab or mountpoint.mount unit file) during system boot leads to a timeout because of device timeout and after i do a systemctl daemon-reload the mount is successful? Detailed information: My system is a Linuxfromscratch 7.5

Re: [systemd-devel] [PATCH] systemctl: systemctl --root=container/ set-default ... is totally borked.

On Thu, Apr 17, 2014 at 01:42:23PM +0200, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Apr 17, 2014 at 10:40:37AM +0200, Jan Chaloupka wrote: On 04/17/2014 04:59 AM, Zbigniew Je;drzejewski-Szmek wrote: On Thu, Apr 17, 2014 at 01:41:51AM +0100, Djalal Harouni wrote: BTW, I've a question, why

Re: [systemd-devel] [PATCH] names: take the registry write lock in kdbus_name_release()

Hi On Fri, Apr 18, 2014 at 3:16 AM, Djalal Harouni tix...@opendz.org wrote: Take the write lock in kdbus_name_release() instead of kdbus_cmd_name_release() in order to reduce the lock hold time. This change permits to convert the kdbus_bus_find_conn_by_id() call to kdbus_conn_find_peer()