After upgrading systemd 208 -> 212, every single cron job creates this
flood in systemd journal:
juuni 09 09:20:01 xps14 crond[15112]: pam_unix(crond:session): session
opened for user root by (uid=0)
juuni 09 09:20:01 xps14 systemd[15113]: pam_unix(systemd-user:session):
session opened for use
Hello.
I have upgraded systemd from 212 to 213 on two my Gentoo boxes, and see
the same regression here: zram swap space does not get activated. It
looks like systemd tries to activate swap before the RUN+=mkswap part of
the udev rule finishes.
Here are the relevant lines from my configurati
El Sun, 8 de Jun 2014 a las 11:44 AM, Leonid Isaev
escribió:
Hi,
On Sun, Jun 08, 2014 at 12:33:44PM +, Rusty Bird wrote:
Date: Sun, 08 Jun 2014 12:33:44 +
From: Rusty Bird
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] [PATCH] Add a network-pre.target to
avo
Hi,
On Sun, Jun 08, 2014 at 12:33:44PM +, Rusty Bird wrote:
> Date: Sun, 08 Jun 2014 12:33:44 +
> From: Rusty Bird
> To: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] [PATCH] Add a network-pre.target to avoid
> firewall leaks
>
> Leonid Isaev:
> > But by the time ne
"touch /forcefsck" leads in deprecated warnings but in fact at least
on Fedora 19 *you need it* because the fsck don't happen otherwise
for sure, the last reboot of the machine below complaind too
so why don't it happen at boot?
Jun 8 14:51:31 localhost systemd-f
On Sun, Jun 08, 2014 at 08:49:10PM +0800, Leslie Zhai wrote:
> Hi Zbyszek,
>
> Thanks for your reply :)
>
> OK, it is enough to collect user space coredump info for bug
> reporter frontend :)
Hi,
if you do polling yourself, sd_journal_wait() is unnecessary and
harmful.
> 1. const char *field,
Hi,
Commit 2dcf7ec6ec added the following to Makefile.am:
+GENERAL_ALIASES += \
+ $(systemunitdir)/systemd-networkd.service
$(pkgsysconfdir)/system/multi-user.target.wants/systemd-networkd.service \
+ $(systemunitdir)/systemd-networkd.service
$(pkgsysconfdir)/system/network-online.t
On Sun, Jun 08, 2014 at 01:57:21PM +0200, Daniel Buch wrote:
> Lets allow LC_ALL=C without corrupted output
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi Mantas,
Thanks for your reply :)
Yes, I use sd_journal_get_fd() API as Zbigniew mentioned
https://github.com/AOSC-Dev/FixMe/blob/master/test/test_systemd_journal.c#L22
But sd_journal_get_data print out no such file or directory error
COREDUMP=ELF
https://github.com/AOSC-Dev/FixMe/blob/ma
Hi Zbyszek,
Thanks for your reply :)
OK, it is enough to collect user space coredump info for bug reporter
frontend :)
1. const char *field, the second parameter of sd_journal_get_data, is
able to set filter to limit the entries, isn't it?
2. I simply init pollfd struct with fds[0].fd = sd
Leonid Isaev:
> But by the time network.target is reached there are no listening services yet,
> are there? So, why would one need a firewall?
Adding to Djalal's and Mantas's examples, the systemd host may also be
a gateway with its firewall configured to forward only *some* packets.
Rusty
sig
https://bugs.freedesktop.org/show_bug.cgi?id=79600
---
Hi Zbigniew,
> Currently my iptables.service has Before=basic.target. Why
> is doing something like that not enough?
Before=basic.target means lots of totally unrelated units can't be
started in parallel to the firewall.
More importantly, y
On 05.06.2014 12:05, Tom Gundersen wrote:
Thanks for the reminder. I'll revert the revert :)
We grew some more features since it was first introduced, so will have
to check out how it all works with tunnels, veth devices etc, but
should definitely have this back for 314.
Cheers,
Tom
Predicta
Lets allow LC_ALL=C without corrupted output
---
src/bus-proxyd/bus-policy.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/bus-proxyd/bus-policy.c b/src/bus-proxyd/bus-policy.c
index 053495c..2df4bf7 100644
--- a/src/bus-proxyd/bus-policy.c
+++ b/src/bus-proxyd/bu
14 matches
Mail list logo
