Am 16.04.2014 06:10, schrieb Andy Johnson:
Hello, systemd-devel,
I saw this in the manpage of systemd-networkd.service (in the systemd git
tree)
systemd-networkd.service, systemd-networkd — Network manager
My question is: is systemd-networkd.service a replacement for the
Network
On 04/14/2014 08:16 PM, Ryan Lortie wrote:
hi,
Hi,
On Mon, Apr 14, 2014, at 12:08, Lennart Poettering wrote:
Au contraire. I am pretty sure that with handling the driver client side
makes things much simpler and closer to classic dbus1.
I agree. No races, after all, in practice.
Before
On 16.04.2014 08:39, Thomas Bächler wrote:
Am 16.04.2014 06:10, schrieb Andy Johnson:
Hello, systemd-devel,
I saw this in the manpage of systemd-networkd.service (in the systemd git
tree)
systemd-networkd.service, systemd-networkd — Network manager
My question is: is
NixOS uses Unix domain sockets for certain host - container
interaction; i.e. the host connects to a socket visible in the
container's directory tree, where the container uses a .socket unit to
spawn the handler program on demand. This worked in systemd 203, but
in 212 fails with foo.socket failed
On Wed, 2014-04-16 at 08:39 +0200, Thomas Bächler wrote:
Am 16.04.2014 06:10, schrieb Andy Johnson:
Hello, systemd-devel,
I saw this in the manpage of systemd-networkd.service (in the systemd git
tree)
systemd-networkd.service, systemd-networkd — Network manager
My question
On Mon, Apr 14, 2014 at 01:07:52AM +0100, Djalal Harouni wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around this, the user must specify the --force switch to be
able to overwrite
create_symlink() do not check the return value of unlink(), this may
confuse the user.
Before the unlink() call we check the 'force' argument. If it is not set
we fail with -EEXIST, otherwise we unlink() the file, therefore the next
symlink() should not fail with -EEXIST (do not count races...).
On Wed, Apr 16, 2014 at 06:39:07PM +0200, Eelco Dolstra wrote:
NixOS uses Unix domain sockets for certain host - container
interaction; i.e. the host connects to a socket visible in the
container's directory tree, where the container uses a .socket unit to
spawn the handler program on demand.
On Thu, Apr 17, 2014 at 01:41:51AM +0100, Djalal Harouni wrote:
On Mon, Apr 14, 2014 at 01:07:52AM +0100, Djalal Harouni wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around
On Mon, Apr 14, 2014 at 01:07:52AM +0100, Djalal Harouni wrote:
Currently systemctl set-default will fail to change the default target
due to the 'default.target' being a symlink which is always the case.
To work around this, the user must specify the --force switch to be
able to overwrite
On Thu, Apr 17, 2014 at 01:47:11AM +0100, Djalal Harouni wrote:
create_symlink() do not check the return value of unlink(), this may
confuse the user.
Before the unlink() call we check the 'force' argument. If it is not set
we fail with -EEXIST, otherwise we unlink() the file, therefore the
11 matches
Mail list logo