On 07/01/2014 01:58 PM, Tom Gundersen wrote:
On Mon, Jun 30, 2014 at 11:47 PM, Matthias Schiffer
mschif...@universe-factory.net wrote:
On 06/24/2014 12:25 PM, Tom Gundersen wrote:
On Tue, Jun 24, 2014 at 12:14 PM, Vasiliy Tolstov v.tols...@selfip.ru
wrote:
Hi. I have very strange task:
Hi,
I am pretty sure at some point systemd-hostnamed was shutting itself
down within 5 minutes of inactivity. It seems like we have lost this
feature. Is the feature removed intentionally?
Thanks,
Umut
___
systemd-devel mailing list
On Wed, Jul 2, 2014 at 9:39 AM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
Hi,
I am pretty sure at some point systemd-hostnamed was shutting itself
down within 5 minutes of inactivity. It seems like we have lost this
feature. Is the feature removed intentionally?
The idle shutdown is
On Wed, Jul 2, 2014 at 8:31 AM, Matthias Schiffer
mschif...@universe-factory.net wrote:
I don't think it's always possible to set the address when an interface
is created; one example would be interfaces that aren't created
explicitly, but as a side effect (I'm thinking of things like the peer
On Wed, Jul 2, 2014 at 2:20 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
Hi,
this is in some sense a continuation of the subject of xz compression
for coredumps.
I've been benchmarking systemd-journal-remote + nc upload speed on
some fake data in which the MESSAGE fields are a
Am 02.07.2014 02:20, schrieb Zbigniew Jędrzejewski-Szmek:
this is in some sense a continuation of the subject of xz compression
for coredumps.
I've been benchmarking systemd-journal-remote + nc upload speed on
some fake data in which the MESSAGE fields are a few kb, big enough to
trigger
On Wed, Jul 2, 2014 at 3:05 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Tue, Jul 01, 2014 at 04:36:47PM +0200, Lennart Poettering wrote:
On Tue, 01.07.14 16:47, microcai (micro...@fedoraproject.org) wrote:
Maybe another option is to improve localectl on the client side to
On Wed, 02.07.14 02:20, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
Hi,
this is in some sense a continuation of the subject of xz compression
for coredumps.
I've been benchmarking systemd-journal-remote + nc upload speed on
some fake data in which the MESSAGE fields are a few
2014-06-25 14:12 GMT+04:00 Michael Olbrich m.olbr...@pengutronix.de:
Hi,
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
network-online.target after network.target' added Before=network.target
dependency to systemd-networkd-wait-online.service. Is that correct? If I
understand
On my embedded system with systemd 213, hostnamed doesn't shutdown
event after 15 minutes.
● systemd-hostnamed.service - Hostname Service
Loaded: loaded
(/mnt/flash/etc/systemd/system/systemd-hostnamed.service; static)
Active: active (running) since Wed 2014-07-02 10:42:10 GMT; 15min ago
Hi,
I'm trying to understand dracut/systemd fsck behaviour, in the context
of an ext4 filesystem root mounted read-only from dracut, remaining
read-only even when the system is fully booted (kiosk-style).
I see that systemd's fstab-generator rightly creates a mount unit for
/sysroot from the
Hi,
I am agreeing with Simon. We use mips and we see the mentioned
impacts. We also see quite size difference (%6 large on systemd-cat
binary text section) which might not be so welcomed on embedded
system.
Umut
On Mon, May 19, 2014 at 12:37 PM, Simon McVittie
simon.mcvit...@collabora.co.uk
On Wed, Jul 02, 2014 at 12:39:54PM +0100, Daniel Drake wrote:
Hi,
I'm trying to understand dracut/systemd fsck behaviour, in the context
of an ext4 filesystem root mounted read-only from dracut, remaining
read-only even when the system is fully booted (kiosk-style).
I see that systemd's
On Wed, Jul 2, 2014 at 1:13 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
Thinking about it, I'm not sure how the new systemd would know that
systemd-fsck@dev-something.service from the initramfs is the same
thing as systemd-fsck-root.service. Maybe that's the problem?
Currently
On Wed, 02.07.14 12:39, Daniel Drake (dr...@endlessm.com) wrote:
Then the system continues booting, switches root, and then
system-fsck-root.service starts from the root fs, and runs fsck on /
again. This is the bit I don't understand - we already checked from
the initramfs, why check again
the main question is *why* is it systemd's business?
that flags are generelly set at the distribution level
and in case of Fedora they can differ between archs
because each arch has it's own %{optflags}
the whole mess exists because upstream projects
don't leave their fingers from that flags at
On Wed, Jul 2, 2014 at 1:36 PM, Lennart Poettering
lenn...@poettering.net wrote:
Then the system continues booting, switches root, and then
system-fsck-root.service starts from the root fs, and runs fsck on /
again. This is the bit I don't understand - we already checked from
the initramfs,
'Twas brillig, and Daniel Drake at 02/07/14 13:29 did gyre and gimble:
On Wed, Jul 2, 2014 at 1:13 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
Thinking about it, I'm not sure how the new systemd would know that
systemd-fsck@dev-something.service from the initramfs is the same
On Wed, 02.07.14 03:05, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Tue, Jul 01, 2014 at 04:36:47PM +0200, Lennart Poettering wrote:
On Tue, 01.07.14 16:47, microcai (micro...@fedoraproject.org) wrote:
Maybe another option is to improve localectl on the client side to
Consider the following situation.
We have foo.target and foo@.service. All instances of foo@.service are
WantedBy=foo.target (and implicitly After=foo.target). So, when foo.target
is activated, all instances of foo@.service are started in parallel.
The question is -- how to run them sequentially?
'Twas brillig, and Daniel Drake at 02/07/14 13:43 did gyre and gimble:
On Wed, Jul 2, 2014 at 1:36 PM, Lennart Poettering
lenn...@poettering.net wrote:
Then the system continues booting, switches root, and then
system-fsck-root.service starts from the root fs, and runs fsck on /
again. This
On Wed, 02.07.14 08:39, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
Hi,
I am pretty sure at some point systemd-hostnamed was shutting itself
down within 5 minutes of inactivity. It seems like we have lost this
feature. Is the feature removed intentionally?
Appears to work correctly
'Twas brillig, and Colin Guthrie at 02/07/14 14:07 did gyre and gimble:
I guess that as most people use initramfs', an extra
ConditionPathExists!=/run/initfamfs/skip-root-fsck wouldn't go astray,
and dracut+co could learn to touch that file if they've properly
analysed and taken care of root
On Sun, 29.06.14 17:50, Leonid Isaev (lis...@umail.iu.edu) wrote:
Hi,
I am seeing the following messages in my syslog on each boot:
--
$ grep link config /var/log/errors.log
2014-06-29T09:31:39.000-04:00 hermes systemd-udevd[246]: Could not apply link
config to br0
On Wed, 02.07.14 17:05, Ivan Shapovalov (intelfx...@gmail.com) wrote:
Consider the following situation.
We have foo.target and foo@.service. All instances of foo@.service are
WantedBy=foo.target (and implicitly After=foo.target). So, when foo.target
is activated, all instances of foo@.service
On Sat, 07.06.14 13:07, Tanu Kaskinen (tanu.kaski...@linux.intel.com) wrote:
Hi,
Currently, systemd symlinks ~/.local/share/systemd/user to
~/.config/systemd/user. I'd prefer to not have that symlink. I'd
want the two locations have different semantics, analogous to the
separation between
On Sat, 07.06.14 07:42, William Giokas (1007...@gmail.com) wrote:
On Sat, Jun 07, 2014 at 01:07:08PM +0300, Tanu Kaskinen wrote:
Hi,
Currently, systemd symlinks ~/.local/share/systemd/user to
~/.config/systemd/user. I'd prefer to not have that symlink. I'd want the
two locations have
On Fri, 30.05.14 18:20, Michal Sekletar (msekl...@redhat.com) wrote:
Sorry for the late response!
Looks good! Applied.
Lennart
--
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
On Wed, Jul 02, 2014 at 03:05:36AM +0200, Zbigniew Jędrzejewski-Szmek wrote:
On Tue, Jul 01, 2014 at 04:36:47PM +0200, Lennart Poettering wrote:
On Tue, 01.07.14 16:47, microcai (micro...@fedoraproject.org) wrote:
Maybe another option is to improve localectl on the client side to
On Wed, Jul 2, 2014 at 4:05 PM, Ivan Shapovalov intelfx...@gmail.com wrote:
Consider the following situation.
We have foo.target and foo@.service. All instances of foo@.service are
WantedBy=foo.target (and implicitly After=foo.target). So, when foo.target
is activated, all instances of
On Wednesday 02 July 2014 at 18:04:36, Mantas Mikulėnas wrote:
On Wed, Jul 2, 2014 at 4:05 PM, Ivan Shapovalov intelfx...@gmail.com wrote:
Consider the following situation.
We have foo.target and foo@.service. All instances of foo@.service are
WantedBy=foo.target (and implicitly
On Wed, Jul 02, 2014 at 03:15:58PM +0200, Lennart Poettering wrote:
On Sun, 29.06.14 17:50, Leonid Isaev (lis...@umail.iu.edu) wrote:
Hi,
I am seeing the following messages in my syslog on each boot:
--
$ grep link config /var/log/errors.log
2014-06-29T09:31:39.000-04:00
On Jul 2, 2014, at 5:39 AM, Daniel Drake dr...@endlessm.com wrote:
Hi,
I'm trying to understand dracut/systemd fsck behaviour, in the context
of an ext4 filesystem root mounted read-only from dracut, remaining
read-only even when the system is fully booted (kiosk-style).
I see that
On Wed, Jul 02, 2014 at 12:33:01PM -0600, Chris Murphy wrote:
On Jul 2, 2014, at 5:39 AM, Daniel Drake dr...@endlessm.com wrote:
Hi,
I'm trying to understand dracut/systemd fsck behaviour, in the context
of an ext4 filesystem root mounted read-only from dracut, remaining
read-only
On Tue, 24.06.14 14:40, Alexander Vladimirov
(alexander.idkfa.vladimi...@gmail.com) wrote:
Seems like remote command execution was broken somewhere around systemd 213
Remote access to systemd 212 host:
[root@host1 ~]# systemctl --version
systemd 212
+PAM -AUDIT -SELINUX -IMA -SYSVINIT
В Wed, 2 Jul 2014 12:33:01 -0600
Chris Murphy li...@colorremedies.com пишет:
On Jul 2, 2014, at 5:39 AM, Daniel Drake dr...@endlessm.com wrote:
Hi,
I'm trying to understand dracut/systemd fsck behaviour, in the context
of an ext4 filesystem root mounted read-only from dracut,
36 matches
Mail list logo
