Hello,
if anybody lurking here and hacking on systemd also likes scheme, I
created bindings for GNU Guile [1]. The API is far from covered, but
journal API and sd_listen* stuff is usable. You can now write socket
activated services in scheme!
[1] https://github.com/jsynacek/guile-systemd
Have fu
Is remote-fs.target somehow dependent/ordered on network.target or
network-online.target? I can't find anything that would suggest it
actually is.
Cheers,
--
Jan Synacek
Software Engineer, Red Hat
signature.asc
Description: PGP signature
___
systemd-d
I have the following setup on a freshly updated Fedora Rawhide machine
with systemd-220-9.fc23.x86_64.
# cat /etc/fstab
[comments left out]
UUID=d5ac823b-d0bd-4f7f-bf4b-5cc82d585a92 / btrfs
subvol=root 0 0
UUID=ec79f233-055c-40fa-98e5-e2d77314913a /boot
See https://github.com/systemd/systemd/pull/5. There are multiple
references to this PR that say " referenced this pull request from
a commit in ", which is hilarious, as those clearly are not
references to this PR. Their commit messages contain the string "#5" and
Github thinks it means a referenc
Hello,
From the following commit onward, systemd doesn't boot properly in
Rawhide. Some device units time out and I'm then dropped into an
emergency shell.
commit f4ac4d1a82e2c468761fffa23841ad886221
Author: Tom Gundersen
Date: Wed Apr 1 13:55:20 2015 +0200
libudev: device - replace b
Hello,
when systemd creates a socket file, it explicitly calls a selinux
procedure to label it. I don't think that is needed, as the kernel does
the right thing when the socket is created. Am I missing something? Why
is the explicit labeling in place?
Cheers,
--
Jan Synacek
Software Engineer, Re
Hi,
test-dhcp-{client,server} are failing in mock:
FAIL: test-dhcp-client
==
Assertion 'client' failed at ../src/libsystemd-network/sd-dhcp-client.c:138,
function sd_dhcp_client_set_request_option(). Ignoring.
Assertion 'client' failed at ../src/libsystemd-network/sd-dhcp-cli
Hello,
what is the difference between emergency, rescue and single-user?
On F21, systemd-216-12.fc21.x86_64, they all boot into something that
presents itself as "Welcome to emergency mode!" and they all require a
root password. In case of booting into emergency.target, I can see
"Starting Emergen
Hello,
currently, when SELINUX=enforcing and SELINUXTYPE= are
set in /etc/selinux/config, systemd refuses to boot with
"Failed to load SELinux policy. Freezing."
Is this really what should happen? If SELINUX is set to permissive or
disabled, though, systemd happily continues booting. I think that
Hello,
commit 539618a0ddc2dc7f0fbe28de2ae0e07b34c81e60
Author: Lennart Poettering
Date: Wed Oct 29 17:06:32 2014 +0100
util: make use of the new getrandom() syscall if it is available when
needing entropy
Doesn't require an fd, and could be a bit faster, so let's make use of
it,
10 matches
Mail list logo
