I need to run Fedora 19 (systemd 204) for a particular piece of
software on a laptop, and I'm having trouble disabling suspend when I
shut the screen. My default target is multi-user.target, and the
laptop is not connected to any external monitors. I made the following
change to /etc/systemd/logind
On Mon, Jun 9, 2014 at 4:42 PM, Reindl Harald wrote:
>
> Am 09.06.2014 22:32, schrieb Leonid Isaev:
>> On Mon, Jun 09, 2014 at 09:19:20PM +0200, Reindl Harald wrote:
>>> [...]
>>>
>>> on our production infrastrcuture these messages would be
>>> *a lot* more than all other logs summarized
>>>
>>> *
On Mon, Jun 09, 2014 at 08:05:35PM +0200, Jan Alexander Steffens (heftig) wrote:
> They shouldn't be executable nor world-readable.
> ---
> tmpfiles.d/systemd.conf | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/tmpfiles.d/systemd.conf b/tmpfiles.d/systemd.conf
On Wed, Jun 04, 2014 at 07:52:56PM -0700, Cameron Norman wrote:
> On Wed, Jun 4, 2014 at 5:31 PM, Luis R. Rodriguez wrote:
> > On Sun, Jun 01, 2014 at 08:15:47AM +0200, Lennart Poettering wrote:
> >> On Fri, 30.05.14 01:29, Luis R. Rodriguez ([email protected]) wrote:
> >>
> >> > I'm cc'ing a few se
On Mon, Jun 09, 2014 at 08:37:18PM +0200, Jan Alexander Steffens wrote:
> On Mon, Jun 9, 2014 at 8:30 PM, Greg KH wrote:
> > Why do you think they should not be?
>
> Executability is just nonsense, while world-readability goes against
> the systemd-journald manpage, which claims that, by default,
The CoreOS crew has already done most of this work by writing a native
Go implementation (rather than wrapping the C APIs).
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
'Twas brillig, and Reindl Harald at 09/06/14 19:57 did gyre and gimble:
> what disturbs me is they warning about "touch /forcefsck" while
> it's currently the *only* option to trigger a recommended fsck
> at boot on a remote-server (and no add kernel params for that
> in the grub-config and remove
Am 09.06.2014 22:32, schrieb Leonid Isaev:
> On Mon, Jun 09, 2014 at 09:19:20PM +0200, Reindl Harald wrote:
>> [...]
>>
>> on our production infrastrcuture these messages would be
>> *a lot* more than all other logs summarized
>>
>> *and* they are spitted to /var/log/messages to make things worst
On Mon, Jun 09, 2014 at 09:19:20PM +0200, Reindl Harald wrote:
> [...]
>
> on our production infrastrcuture these messages would be
> *a lot* more than all other logs summarized
>
> *and* they are spitted to /var/log/messages to make things worst
>
> > But why can't you write a syslog filter whi
Am 09.06.2014 21:26, schrieb Alexander E. Patrakov:
> 10.06.2014 00:57, Reindl Harald wrote:
>>
>> Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
>>> 10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
> 'Twas brillig, and Reindl Harald at 08/06/1
Am 09.06.2014 21:07, schrieb Leonid Isaev:
> On Mon, Jun 09, 2014 at 08:08:43PM +0200, Reindl Harald wrote:
>> all the decades before crond did run fine, logs exactly what
>> you need to know if /var/log/secure and /var/log/crond
>> without writing *hundret thousands* loglines all day long
>> on
10.06.2014 00:57, Reindl Harald wrote:
Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" leads in deprecated warnin
On Mon, Jun 09, 2014 at 08:08:43PM +0200, Reindl Harald wrote:
> Date: Mon, 09 Jun 2014 20:08:43 +0200
> From: Reindl Harald
> To: [email protected]
> Subject: Re: [systemd-devel] How to quiet cron sessions logging with
> systemd-212?
> User-Agent: Mozilla/5.0 (X11; Linux x86_64
Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
> 10.06.2014 00:04, Reindl Harald wrote:
>>
>> Am 09.06.2014 17:05, schrieb Colin Guthrie:
>>> 'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" leads in deprecated warnings but in fact at least
Hello!
We've been working on golang bindings to the systemd journal interface
(sd-journal.h), as well as a higher level go API which builds on the bindings.
The immediate goal is to replace the use of forked calls to journalctl in a
project. To that end, we've been wrapping only the subset o
10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" leads in deprecated warnings but in fact at least
on Fedora 19 *you need it* because the fsck don't happen otherwise
fo
[maintainers of zram CC:ed, in order to alert them of this
incompatibility with a setup published by Gentoo and possibly picked up
by others]
[Pacho Ramos CC:ed as a person who asked about zram here before and who
can remove the non-working instruction listed at
http://wiki.gentoo.org/wiki/Zr
On Mon, Jun 9, 2014 at 8:30 PM, Greg KH wrote:
> Why do you think they should not be?
Executability is just nonsense, while world-readability goes against
the systemd-journald manpage, which claims that, by default, only
users in the systemd-journal system group can read journals not their
own.
On Mon, Jun 09, 2014 at 08:05:35PM +0200, Jan Alexander Steffens (heftig) wrote:
> They shouldn't be executable nor world-readable.
Why do you think they should not be?
> ---
> tmpfiles.d/systemd.conf | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/tmpfiles.d
Am 09.06.2014 17:05, schrieb Colin Guthrie:
> 'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
>> "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
Am 09.06.2014 17:28, schrieb Leonid Isaev:
> On Mon, Jun 09, 2014 at 10:48:31AM +0300, Leho Kraav wrote:
>> Date: Mon, 09 Jun 2014 10:48:31 +0300
>> From: Leho Kraav
>> To: Reindl Harald ,
>> [email protected]
>> Subject: Re: [systemd-devel] How to quiet cron sessions logging
They shouldn't be executable nor world-readable.
---
tmpfiles.d/systemd.conf | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/tmpfiles.d/systemd.conf b/tmpfiles.d/systemd.conf
index c5910f8..d6c4da3 100644
--- a/tmpfiles.d/systemd.conf
+++ b/tmpfiles.d/systemd.conf
@@
Alexander E. Patrakov schrieb:
> 09.06.2014 19:26, Kai Krakow wrote:
>> Alexander E. Patrakov schrieb:
>>
>>> 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
On Mon, Jun 9, 2014 at 4:08 PM, Dave Reisner wrote:
> On Mon, Jun 09, 2014 at 10:12:35AM +0200, Tom Gundersen wrote:
>> Hi Dave,
>>
>> On Sun, Jun 8, 2014 at 3:37 PM, Dave Reisner wrote:
>> > Commit 2dcf7ec6ec added the following to Makefile.am:
>> >
>> > +GENERAL_ALIASES += \
>> > + $(syst
'Twas brillig, and Dave Reisner at 09/06/14 15:08 did gyre and gimble:
>>> > > On a related topic, could we please stop shipping hardcoded symlinks in
>>> > > /etc in favor of documented reccomendations for downstream packagers?
>> >
>> > I believe the aim here is to make "./autogen.sh c && make &
On Mon, Jun 09, 2014 at 07:57:29AM +, Rusty Bird wrote:
> Date: Mon, 09 Jun 2014 07:57:29 +
> From: Rusty Bird
> To: [email protected]
> Subject: Re: [systemd-devel] [PATCH] Add a network-pre.target to avoid
> firewall leaks
>
> Hi Leonid,
>
> > On Sun, Jun 08, 2014 at
On Mon, Jun 09, 2014 at 10:48:31AM +0300, Leho Kraav wrote:
> Date: Mon, 09 Jun 2014 10:48:31 +0300
> From: Leho Kraav
> To: Reindl Harald ,
> [email protected]
> Subject: Re: [systemd-devel] How to quiet cron sessions logging with
> systemd-212?
> User-Agent: Mozilla/5.0 (X11;
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
> "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 hap
On Mon, Jun 9, 2014 at 4:31 PM, Alexander E. Patrakov
wrote:
> 09.06.2014 20:11, Kay Sievers wrote:
>>
>> On Mon, Jun 9, 2014 at 4:02 PM, Alexander E. Patrakov
>> wrote:
>>>
>>> 09.06.2014 19:26, Kai Krakow wrote:
Alexander E. Patrakov schrieb:
> I have upgraded systemd f
09.06.2014 20:11, Kay Sievers wrote:
On Mon, Jun 9, 2014 at 4:02 PM, Alexander E. Patrakov
wrote:
09.06.2014 19:26, Kai Krakow wrote:
Alexander E. Patrakov schrieb:
I have upgraded systemd from 212 to 213 on two my Gentoo boxes, and see
the same regression here: zram swap space does not ge
On Mon, Jun 9, 2014 at 4:02 PM, Alexander E. Patrakov
wrote:
> 09.06.2014 19:26, Kai Krakow wrote:
>>
>> Alexander E. Patrakov schrieb:
>>
>>> 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
On Mon, Jun 09, 2014 at 10:12:35AM +0200, Tom Gundersen wrote:
> Hi Dave,
>
> On Sun, Jun 8, 2014 at 3:37 PM, Dave Reisner wrote:
> > Commit 2dcf7ec6ec added the following to Makefile.am:
> >
> > +GENERAL_ALIASES += \
> > + $(systemunitdir)/systemd-networkd.service
> > $(pkgsysconfdir)/sys
09.06.2014 19:26, Kai Krakow wrote:
Alexander E. Patrakov schrieb:
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
Alexander E. Patrakov schrieb:
> 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 re
On 7 Jun 2014 21:57, "Unknown" wrote:
>
> Hello. It is said in the man systemd-netword-wait-online.service:
>
> >systemd-networkd-wait-online is a one-shot system service that waits
> >for the network to be configured. By default, it will wait for all
> >links it is aware of and which are managed
I think there's also another problem – logind starts the user manager
instance for cronjobs while it shouldn't do so for batch stuff. Probably a
PAM configuration issue.
--
Mantas Mikulėnas
On Jun 9, 2014 9:34 AM, "Leho Kraav" wrote:
> After upgrading systemd 208 -> 212, every single cron job
Hi Dave,
On Sun, Jun 8, 2014 at 3:37 PM, Dave Reisner wrote:
> Commit 2dcf7ec6ec added the following to Makefile.am:
>
> +GENERAL_ALIASES += \
> + $(systemunitdir)/systemd-networkd.service
> $(pkgsysconfdir)/system/multi-user.target.wants/systemd-networkd.service \
> + $(systemunitdi
Hi Leonid,
> On Sun, Jun 08, 2014 at 12:33:44PM +, Rusty Bird wrote:
>> 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.
> If systemd itself is a server (you mean journald really, yes?)
"systemd
On 09.06.2014 10:43, Reindl Harald wrote:
nobody cares because the developers point of view is that what is
interesting for them needs to be also faced by the sysadmin
otherwise this would be only logged in debug-mode and bugreports
not closed: https://bugzilla.redhat.com/show_bug.cgi?id=1072368
39 matches
Mail list logo
