On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net wrote:
To hook up local name service
clients people should use the nss-resolve NSS module, which ensures
that gethostbyname() and friends use resolved as backend.
I suppose then non-glibc clients should deal with that on its
On 2015-06-15 19:38, Lennart Poettering wrote:
On Mon, 15.06.15 19:23, Goffredo Baroncelli (kreij...@inwind.it) wrote:
On 2015-06-15 12:46, Lennart Poettering wrote:
On Sat, 13.06.15 17:09, Goffredo Baroncelli (kreij...@libero.it) wrote:
Further, the problem will be more intense in this eg.
On Wed, 17 Jun 2015 19:04:34 +0200, Lennart Poettering wrote:
On Wed, 17.06.15 18:57, Jean Delvare (jdelv...@suse.de) wrote:
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if
On Wed, 17.06.15 19:48, Igor Bukanov (i...@mir2.org) wrote:
On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net wrote:
To hook up local name service
clients people should use the nss-resolve NSS module, which ensures
that gethostbyname() and friends use resolved as backend.
On 18 Jun 2015 3:51 am, Lennart Poettering lenn...@poettering.net wrote:
On Wed, 17.06.15 19:48, Igor Bukanov (i...@mir2.org) wrote:
On 17 June 2015 at 15:27, Lennart Poettering lenn...@poettering.net
wrote:
To hook up local name service
clients people should use the nss-resolve NSS
In which case:
1. The man pages, to me, imply that I should be able to get everything that
‘status' shows using ‘show' because it says:
This function is intended to generate human-readable output. If you are
looking for computer-parsable output, use show instead.” (and vice versa)
This
On Jun 17, 2015, at 1:07, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Tue, Jun 16, 2015 at 11:39 PM, Johannes Ernst
johannes.er...@gmail.com wrote:
I have a root filesystem in directory foo/
It has symlink
foo/etc/resolv.conf - /run/systemd/resolve/resolv.conf
When I’m
On Wed, 17.06.15 13:34, Johannes Ernst (johannes.er...@gmail.com) wrote:
In which case:
1. The man pages, to me, imply that I should be able to get everything that
‘status' shows using ‘show' because it says:
This function is intended to generate human-readable output. If you are
On Jun 17, 2015, at 14:09, Lennart Poettering lenn...@poettering.net wrote:
On Wed, 17.06.15 13:34, Johannes Ernst (johannes.er...@gmail.com) wrote:
2. So how do I get at the IP address of the container in a way that
is easily parseable?
make sure nss-mymachines is installed and
В Wed, 17 Jun 2015 23:02:02 +0200
Lennart Poettering lenn...@poettering.net пишет:
On Wed, 17.06.15 21:10, Goffredo Baroncelli (kreij...@libero.it) wrote:
Well, /bin/mount is not a daemon, and it should not be one.
My helper is not a deamon; you was correct the first time: it blocks
On 06/17/2015 12:34 PM, Lennart Poettering wrote:
On Mon, 18.05.15 18:45, Eric Cook (l...@gmx.com) wrote:
By the time __systemctl is called, --user/--system are shifted out of
`words' by _arguments. This patch queries the array sooner.
In the case that both --user and --system are on the
On Wed, 17.06.15 21:10, Goffredo Baroncelli (kreij...@libero.it) wrote:
Well, /bin/mount is not a daemon, and it should not be one.
My helper is not a deamon; you was correct the first time: it blocks
until all needed/enough devices are appeared.
Anyway this should not be different from
On Wed, 17 Jun 2015 12:02:27 +0200, Lennart Poettering wrote:
On Wed, 17.06.15 11:26, Jean Delvare (jdelv...@suse.de) wrote:
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if
On Wed, 17.06.15 11:22, Thomas Blume (thomas.bl...@suse.com) wrote:
The systemctl daemon-reexec and daemon-reload documentation
in the manpage is a bit ambiguous. It suggests that daemon-reload reloads the
configuration of the manager itself (e.g. the [Manager] section in
2015-06-17 16:40 GMT+08:00 Reindl Harald h.rei...@thelounge.net:
Am 17.06.2015 um 05:06 schrieb cee1:
2015-06-16 0:21 GMT+08:00 Lennart Poettering lenn...@poettering.net:
On Mon, 15.06.15 23:33, cee1 (fykc...@gmail.com) wrote:
Hi,
I maybe got confused.
First,
Am 17.06.2015 um 14:21 schrieb cee1:
2015-06-17 16:40 GMT+08:00 Reindl Harald h.rei...@thelounge.net:
systemd-random-seed.service will load the seed on disk to
/dev/urandom, and save a seed to disk when shutdown, right?
The article at http://www.2uo.de/myths-about-urandom/ suggests us
saving
Hi Johannes,
there is a tmpfiles.d rule in your container that creates that
snapshot if it is not there yet.
I started to create a var/lib/machines directory in the container as
part of the container creation process, which prevents systemd 219
from creating the btrfs snapshot there.
On Mittwoch 2015-06-17 13:16, Lennart Poettering wrote:
The systemctl daemon-reexec and daemon-reload documentation
in the manpage is a bit ambiguous. It suggests that daemon-reload reloads the
configuration of the manager itself (e.g. the [Manager] section in
/etc/systemd/system.conf). It
Hi
On Wed, Jun 17, 2015 at 5:53 AM, Johannes Ernst
johannes.er...@gmail.com wrote:
Are those supposed to produce the same information, just formatted
differently (man vs machine per man page)?
I’m failing to convince ‘show’ to give me the container’s IP address, while
‘status’ has all of
Hi
On Tue, Jun 16, 2015 at 11:32 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 16.06.15 22:54, Krzesimir Nowak (krzesi...@endocode.com) wrote:
That reminds me of a bug (or not-a-bug) in go-dbus [1] - it also generates
flat hierarchy. This is a problem for tools like d-feet -
On Tue, 2015-06-16 at 19:53 +0200, Thomas H.P. Andersen wrote:
On Thu, May 7, 2015 at 5:47 PM, Pavel Odvody podv...@redhat.com wrote:
Signed-off-by: Pavel Odvody podv...@redhat.com
---
src/import/pull.c | 28 +---
1 file changed, 17 insertions(+), 11 deletions(-)
Hi
On Tue, Jun 16, 2015 at 11:39 PM, Johannes Ernst
johannes.er...@gmail.com wrote:
I have a root filesystem in directory foo/
It has symlink
foo/etc/resolv.conf - /run/systemd/resolve/resolv.conf
When I’m booting the container:
sudo systemd-nspawn --directory foo --boot
I’m
Hi,
I'm so sorry for not giving you more details, I'm a freshman here, but I'll
try to do better in the future.
I will give the answers under each of the questions .
At 2015-06-16 18:54:23, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Tue, Jun 16, 2015 at 12:07 PM, eshark
On Wed, 17.06.15 10:13, David Herrmann (dh.herrm...@gmail.com) wrote:
Hi
On Wed, Jun 17, 2015 at 5:53 AM, Johannes Ernst
johannes.er...@gmail.com wrote:
Are those supposed to produce the same information, just formatted
differently (man vs machine per man page)?
I’m failing to
On Wed, 17.06.15 11:26, Jean Delvare (jdelv...@suse.de) wrote:
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if WDIOS_DISABLECARD is passed and the ioctl is not
implemented, however
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if WDIOS_DISABLECARD is passed and the ioctl is not
implemented, however failing when WDIOS_ENABLECARD is passed and the
ioctl is not implemented
Am 17.06.2015 um 05:06 schrieb cee1:
2015-06-16 0:21 GMT+08:00 Lennart Poettering lenn...@poettering.net:
On Mon, 15.06.15 23:33, cee1 (fykc...@gmail.com) wrote:
Hi,
I maybe got confused.
First, systemd-random-seed.service will save a seed from
/dev/urandom when shutdown, and load that seed
Hi,
With my kdbus broadcast patch, I found that the systemd process would
endlessly emit the signal type=signal sender=:1.2 destination=n/a
object=/org/freedesktop/systemd1/agent interface=org.freedesktop.systemd1.Agent
member=Released .What does this signal mean ?
I searched
The systemctl daemon-reexec and daemon-reload documentation
in the manpage is a bit ambiguous. It suggests that daemon-reload reloads the
configuration of the manager itself (e.g. the [Manager] section in
/etc/systemd/system.conf). It should be pointed out that it only reloads the
configuration
On Wed, Jun 17, 2015 at 2:28 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 17.06.2015 um 14:21 schrieb cee1:
2015-06-17 16:40 GMT+08:00 Reindl Harald h.rei...@thelounge.net:
systemd-random-seed.service will load the seed on disk to
/dev/urandom, and save a seed to disk when shutdown,
Hello,
perhaps I missed something, but it seems that systemd-resolved cannot
be configured to serve the same role as dnsmasq and be a DNS server
for local machine. I.e. I cannot just have nameserver 127.0.0.1 in
/ertc/resolv.conf and get LLMNR resolution working for progams that
only use
On Wed, 17.06.15 15:19, Igor Bukanov (i...@mir2.org) wrote:
Hello,
perhaps I missed something, but it seems that systemd-resolved cannot
be configured to serve the same role as dnsmasq and be a DNS server
for local machine. I.e. I cannot just have nameserver 127.0.0.1 in
/ertc/resolv.conf
The messages about several sysfs paths per device aren't caused by
volume labels as seen in /dev/disk/by-label only.
On GPT systems they seem to be triggered by identical partition labels
corresponding to variable PARTLABEL in output of blkid as well.
Also, they can be seen launching Arch Linux
On Wed, 17.06.15 15:44, Peter Mattern (matte...@arcor.de) wrote:
The messages about several sysfs paths per device aren't caused by volume
labels as seen in /dev/disk/by-label only.
On GPT systems they seem to be triggered by identical partition labels
corresponding to variable PARTLABEL in
On Wed, 17.06.15 16:04, Reindl Harald (h.rei...@thelounge.net) wrote:
Please keep such comments to yourself or you will be
moderated again
you threaten everytime you personally don't agree is a better style?
Congratulations, I just put you back on moderation.
Lennart
--
Lennart
On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote:
2015-06-17 16:40 GMT+08:00 Reindl Harald h.rei...@thelounge.net:
Am 17.06.2015 um 05:06 schrieb cee1:
2015-06-16 0:21 GMT+08:00 Lennart Poettering lenn...@poettering.net:
On Mon, 15.06.15 23:33, cee1 (fykc...@gmail.com) wrote:
Am 17.06.2015 um 14:51 schrieb Kay Sievers:
On Wed, Jun 17, 2015 at 2:28 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 17.06.2015 um 14:21 schrieb cee1:
2015-06-17 16:40 GMT+08:00 Reindl Harald h.rei...@thelounge.net:
systemd-random-seed.service will load the seed on disk to
2015-06-17 22:03 GMT+08:00 Lennart Poettering lenn...@poettering.net:
On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote:
What I means is:
1. Load a saved seed to /dev/urandom.
2. The service read /dev/random, which will block until kernel thinks
there's enough entropy - then the Random
On Wed, 17.06.15 23:08, cee1 (fykc...@gmail.com) wrote:
2015-06-17 22:03 GMT+08:00 Lennart Poettering lenn...@poettering.net:
On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote:
What I means is:
1. Load a saved seed to /dev/urandom.
2. The service read /dev/random, which will block
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if WDIOS_DISABLECARD is passed and the ioctl is not
implemented, however failing when WDIOS_ENABLECARD is passed and the
ioctl is not implemented
On Wed, 17.06.15 18:57, Jean Delvare (jdelv...@suse.de) wrote:
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if WDIOS_DISABLECARD is passed and the ioctl is not
implemented, however
On Wed, 10.06.15 14:40, HATAYAMA Daisuke (d.hatay...@jp.fujitsu.com) wrote:
From 398deee74edb06b54b8a74c25697cd6d977d8f2d Mon Sep 17 00:00:00 2001
From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com
Date: Wed, 10 Jun 2015 14:10:31 +0900
Subject: [PATCH] selinux: fix missing SELinux unit access
On Wed, 03.06.15 14:59, Karel Zak (k...@redhat.com) wrote:
The current implementation directly monitor /proc/self/mountinfo and
/run/mount/utab files. It's really not optimal because utab file is
private libmount stuff without any official guaranteed semantic.
The libmount since v2.26
2015-06-17 23:15 GMT+08:00 Lennart Poettering lenn...@poettering.net:
That don't mean blocking boot, but a service, let's say
systemd-random-seed.service:
1. systemd-random-seed.service loads a seed from disk to /dev/urandom
2. systemd-random-seed.service tells systemd I'm ready (sd_notify())
2015-06-17 23:38 GMT+08:00 Reindl Harald h.rei...@thelounge.net:
Am 17.06.2015 um 17:08 schrieb cee1:
2015-06-17 22:03 GMT+08:00 Lennart Poettering lenn...@poettering.net:
On Wed, 17.06.15 20:21, cee1 (fykc...@gmail.com) wrote:
What I means is:
1. Load a saved seed to /dev/urandom.
2.
On Wed, 17.06.15 17:49, Jean Delvare (jdelv...@suse.de) wrote:
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if WDIOS_DISABLECARD is passed and the ioctl is not
implemented, however
On Wed, 17 Jun 2015 18:00:58 +0200, Lennart Poettering wrote:
On Wed, 17.06.15 17:49, Jean Delvare (jdelv...@suse.de) wrote:
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if
On Wed, 17.06.15 09:09, Pavel Odvody (podv...@redhat.com) wrote:
-tag = latest;
+reference = latest;
}
This part does not look correct. Any value that we set for
reference/name in the digest part will be overwritten in the next
block. I
Not all watchdog drivers implement WDIOC_SETOPTIONS. Drivers which do
not implement it have their device always enabled. So it's fine to
report an error if WDIOS_DISABLECARD is passed and the ioctl is not
implemented, however failing when WDIOS_ENABLECARD is passed and the
ioctl is not implemented
B1;4002;0cOn Wed, 17.06.15 23:45, cee1 (fykc...@gmail.com) wrote:
2015-06-17 23:15 GMT+08:00 Lennart Poettering lenn...@poettering.net:
That don't mean blocking boot, but a service, let's say
systemd-random-seed.service:
1. systemd-random-seed.service loads a seed from disk to /dev/urandom
On Thu, 18.06.15 00:00, cee1 (fykc...@gmail.com) wrote:
First it seeds /dev/urandom
Second, seed /dev/random will not increase the entropy without using
ioctl (please see
https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg32555.html)
Though, some other services may read
51 matches
Mail list logo
