On Tue, Jun 10, 2014 at 5:50 PM, Lennart Poettering
wrote:
> On Tue, 10.06.14 13:58, Mike Gilbert (flop...@gentoo.org) wrote:
>
>> > Symlinks should probably just be considered different type of file, that
>> > have a contents and stuff. The contents is usually a file name, and
>> > there's a size
On Tue, 10.06.14 13:58, Mike Gilbert (flop...@gentoo.org) wrote:
> > Symlinks should probably just be considered different type of file, that
> > have a contents and stuff. The contents is usually a file name, and
> > there's a size limit, but other than that it's just a magic kind of
> > file, wh
---
README |4
1 file changed, 4 insertions(+)
diff --git a/README b/README
index f01087f..011c7f6 100644
--- a/README
+++ b/README
@@ -80,6 +80,10 @@ REQUIREMENTS:
CONFIG_TMPFS_XATTR
CONFIG_SECCOMP
+Required for CPUShares in resource control unit settings
2014-06-10 19:44 GMT+02:00 Lennart Poettering :
> I figure we don't really need network-pre.target, as units that want to
> run before the network is up should just use:
>
> Before=systemd-networkd.service basic.target
>
> THis is enough since network management services like
> NM are normal se
2014-06-10 19:44 GMT+02:00 Lennart Poettering :
> I figure we don't really need network-pre.target, as units that want to
> run before the network is up should just use:
>
> Before=systemd-networkd.service basic.target
>
> THis is enough since network management services like
> NM are normal se
On Jun 9, 2014, at 5:24 PM, Colin Guthrie wrote:
> '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 ad
On 10/06/14 18:58, Mike Gilbert wrote:
> The problem with installing these symlinks as part of a package is
> that the user may have removed them from /etc/systemd using systemctl
> disable.
...
> If rpm or dpkg have a way to detect when the sysadmin has removed a
> file and will not replace that f
On Tue, Jun 10, 2014 at 1:32 PM, Lennart Poettering
wrote:
> On Tue, 10.06.14 13:10, Dave Reisner (d...@falconindy.com) wrote:
>
>> Perhaps there's a middle ground we can find. Tom mentioned the idea of
>> a "package" mode during configuration. How about a simpler idea -- if
>> DESTDIR is empty, a
On Tue, 10.06.14 18:53, Lennart Poettering (lenn...@poettering.net) wrote:
> On Fri, 06.06.14 12:53, Rusty Bird (rustyb...@openmailbox.org) wrote:
>
> Humm. I can't say I particularly like the idea, but I can't dissmiss
> this either, I figure we have to do something like this.
>
> However, if w
On Tue, Jun 10, 2014 at 07:32:56PM +0200, Lennart Poettering wrote:
> Symlinks should probably just be considered different type of file, that
> have a contents and stuff. The contents is usually a file name, and
> there's a size limit, but other than that it's just a magic kind of
> file, where th
On Tue, 10.06.14 20:00, Mantas Mikulėnas (graw...@gmail.com) wrote:
Ouch. Appears I hit "replace" a bit too eargerly...
Applied!
Thanks!
> ---
> units/user/systemd-bus-pro...@.service.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/units/user/systemd-bus-pro...@.se
On Tue, 10.06.14 13:10, Dave Reisner (d...@falconindy.com) wrote:
> Perhaps there's a middle ground we can find. Tom mentioned the idea of
> a "package" mode during configuration. How about a simpler idea -- if
> DESTDIR is empty, add the symlinks. Otherwise, don't.
This sounds fragile... people
On Tue, 10.06.14 20:05, Leho Kraav (l...@kraav.com) wrote:
>
> On 09.06.2014 09:33, Leho Kraav wrote:
> >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
On Tue, 10.06.14 19:03, Leho Kraav (l...@kraav.com) wrote:
>
> On 10.06.2014 19:01, Lennart Poettering wrote:
> >>
> >>In the meantime mgilbert's suggestion for using EDIT **loginctl
> >>enable-linger**
> >>command seems to accomplish the goal of quieting cron logging. Any
> >>side effects to co
On Wed, 28.05.14 11:24, Maciej Wereski (m.were...@partner.samsung.com) wrote:
> >When the function is called the buffer is filled with 36 chars, and we
> >then strip the non-hex-chars, so that 34 chars result. But the function
> >signature should still indicate that we need 36 chars initially..
>
On Tue, Jun 10, 2014 at 7:25 PM, Nicholas Faustini wrote:
> Hi,
>
> I have an issue with the following systemd behavior (from manual):
>
> Mount points created at runtime (independently of unit files or /etc/fstab)
> will be monitored by systemd and appear like any other mount unit in
> systemd. S
On Tue, Jun 3, 2014 at 7:44 PM, Ronny Chevalier
wrote:
> It was forgotten in b1e90ec515408aec2702522f6f68c4920b56375b
>
> See https://bugs.freedesktop.org/show_bug.cgi?id=79582
Applied.
Thanks,
Kay
___
systemd-devel mailing list
systemd-devel@lists.fre
- Original Message -
> From: "Brandon Philips"
> To: "Dan Mace"
> Cc: appinfra-l...@redhat.com, systemd-devel@lists.freedesktop.org
> Sent: Tuesday, June 10, 2014 1:08:59 PM
> Subject: Re: [systemd-devel] Soliciting feedback for golang bindings to the
> systemd journal C API
>
> On Mon,
Am 10.06.2014 18:01, schrieb Lennart Poettering:
> On Tue, 10.06.14 13:24, Leho Kraav (l...@kraav.com) wrote:
>> On 10.06.2014 13:20, Lennart Poettering wrote:
>>> On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
>>>
After upgrading systemd 208 -> 212, every single cron job creates
On Tue, Jun 10, 2014 at 6:07 AM, Dan Mace wrote:
>> Subject: Re: [systemd-devel] Soliciting feedback for golang bindings to the
>> systemd journal C API
>>
>> The CoreOS crew has already done most of this work by writing a native
>> Go implementation (rather than wrapping the C APIs).
>>
>
> Can
On Tue, Jun 10, 2014 at 06:26:47PM +0200, Lennart Poettering wrote:
> On Sun, 08.06.14 09:37, Dave Reisner (d...@falconindy.com) wrote:
>
> > On a related topic, could we please stop shipping hardcoded symlinks in
> > /etc in favor of documented reccomendations for downstream packagers?
>
> Hmm,
On Mon, Jun 9, 2014 at 11:56 AM, Dan Mace wrote:
> http://fpaste.org/107299/14019224/
Hrm, odd. Was it with the given tests? I will try it out and see if I
can reproduce. I don't see anything immediately wrong in the code.
Thanks,
Brandon
___
syste
On Wed, Jun 4, 2014 at 11:40 PM, Thomas H.P. Andersen wrote:
> From: Thomas Hindoe Paaboel Andersen
>
> The return value from udev_enumerate_scan_devices was stored but
> never used. I assume this was meant to be checked.
Applied.
Thanks,
Kay
___
syst
On 09.06.2014 09:33, Leho Kraav wrote:
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-
On Sat, 31.05.14 22:28, Ronny Chevalier (chevalier.ro...@gmail.com) wrote:
Thanks! Applied!
> since v212 calling systemctl status without arguments
> will show a overall system state
> ---
> test/TEST-01-BASIC/test.sh | 2 +-
> test/TEST-02-CRYPTSETUP/test.sh | 2 +-
> 2 files changed, 2 in
On Mon, 02.06.14 16:47, Mantas Mikulėnas (graw...@gmail.com) wrote:
I commited this one a while back. Thanks!
> ---
> man/sd-journal.xml | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/man/sd-journal.xml b/man/sd-journal.xml
> index 7a05aee..d3dc57f 100644
> --- a
---
units/user/systemd-bus-pro...@.service.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/units/user/systemd-bus-pro...@.service.in
b/units/user/systemd-bus-pro...@.service.in
index 68f59f5..2f4df7c 100644
--- a/units/user/systemd-bus-pro...@.service.in
+++ b/units/user/sy
On Thu, 05.06.14 23:59, Denis Tikhomirov (dvtikhomi...@gmail.com) wrote:
Thanks!
Applied!
>
> On Thu, Jun 05, 2014 at 08:37:20AM +0200, Lennart Poettering wrote:
> > The patch is line-broken, please send an uncorrupted patch!
> I am very sorry, I forgot that my client limits line width. I will
On Fri, 06.06.14 12:53, Rusty Bird (rustyb...@openmailbox.org) wrote:
Humm. I can't say I particularly like the idea, but I can't dissmiss
this either, I figure we have to do something like this.
However, if we do this, then this needs to be a "passive" target, see
systemd.special(7), under "Spec
On Fri, 06.06.14 23:06, Colin King (colin.k...@canonical.com) wrote:
Applied by Zbigniew.
Thanks!
> From: Colin Ian King
>
> Signed-off-by: Colin Ian King
> ---
> src/core/busname.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/core/busname.c b/src/core/busnam
On Sun, 08.06.14 09:37, Dave Reisner (d...@falconindy.com) wrote:
> On a related topic, could we please stop shipping hardcoded symlinks in
> /etc in favor of documented reccomendations for downstream packagers?
Hmm, well. The way automake currently works is that all config files are
overwritten
Hi,
I have an issue with the following systemd behavior (from manual):
Mount points created at runtime (independently of unit files or /etc/fstab)
will be monitored by systemd and appear like any other mount unit in systemd.
See /proc/self/mountinfo description in proc(5).
I need to manage mount
On Tue, 10.06.14 14:31, Ivan Shapovalov (intelfx...@gmail.com) wrote:
> It's more interesting, why a logind session is ever being created for the
> cron job...
> It shouldn't be that way, or do I misunderstand something?
We should create a logind session for all sessions of normal users. It
does
On 10.06.2014 19:01, Lennart Poettering wrote:
In the meantime mgilbert's suggestion for using EDIT **loginctl enable-linger**
command seems to accomplish the goal of quieting cron logging. Any
side effects to consider?
Well, you keep the systemd user instance running all the time then
instead
On Tue, 10.06.14 13:24, Leho Kraav (l...@kraav.com) wrote:
>
> On 10.06.2014 13:20, Lennart Poettering wrote:
> >On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
> >
> >>After upgrading systemd 208 -> 212, every single cron job creates
> >>this flood in systemd journal:
> >
> >>Can I qu
On Tue, Jun 10, 2014 at 6:07 AM, Dan Mace wrote:
> Which only handles writes via the Unix socket. The implementation we're
> prototyping supports journal queries in ways that (to my knowledge) aren't
> possible without either forking to external tools (e.g. journalctl) or
> linking to sd-journ
On Tue, Jun 10, 2014 at 3:51 PM, Christian Hesse wrote:
> Arguments were wrong order, no?
Applied.
Thanks,
Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Arguments were wrong order, no?
This fixes commits:
e918a1b5a94f270186dca59156354acd2a596494
3d06f4183470d42361303086ed9dedd29c0ffc1b
---
src/udev/udevd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/udev/udevd.c b/src/udev/udevd.c
index 0f3f3f0..160360e 100644
---
- Original Message -
> From: "David Timothy Strauss"
> To: "Dan Mace"
> Cc: appinfra-l...@redhat.com, "systemd Mailing List"
>
> Sent: Monday, June 9, 2014 8:29:11 PM
> Subject: Re: [systemd-devel] Soliciting feedback for golang bindings to the
> systemd journal C API
>
> The CoreOS c
Am 10.06.2014 12:20, schrieb Lennart Poettering:
> On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
>
>> After upgrading systemd 208 -> 212, every single cron job creates
>> this flood in systemd journal:
>
>> Can I quiet this down somehow?
>
> The idea with the journal is that we lo
On Monday 09 June 2014 at 23:32:28, Mike Gilbert wrote:
> 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 mess
On 10.06.2014 13:20, Lennart Poettering wrote:
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
After upgrading systemd 208 -> 212, every single cron job creates
this flood in systemd journal:
Can I quiet this down somehow?
The idea with the journal is that we log everything that
On Mon, 09.06.14 09:33, Leho Kraav (l...@kraav.com) wrote:
> After upgrading systemd 208 -> 212, every single cron job creates
> this flood in systemd journal:
> Can I quiet this down somehow?
The idea with the journal is that we log everything that happens on the
system, without exceptions, wit
On Mon, 09.06.14 12:01, Mantas Mikulėnas (graw...@gmail.com) wrote:
> 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.
Nope. This is intentional. A session is a session is
(Ahh, critical boot components that depend on Perl. And to think people
complain about systemd.)
systemd installs a /usr/lib/sysctl.d/*-coredump.conf which changes
kernel.core_pattern so that the dumps are written to the journal.
You can override it through /etc/sysctl.d to put the dumps in, for
Hi,
I have recently experienced a massive coredump at startup.
I upgraded perl from 5.18 to 5.20 in Arch Linux, and apparmor loads
massive profiles at boot (which depends on perl), so I can't login
through tty.
I have autologin enabled but no bash prompt, only coredump messages.
So I wonder if
46 matches
Mail list logo
