2013/5/7 Lennart Poettering lenn...@poettering.net:
* libsystemd-logind.so gained a new call
sd_get_machine_names() to enumerate running containers and
VMs (currently only supported by very new libvirt and
nspawn). sd_login_monitor can now be used to watch
On Tue, May 07, 2013 at 12:10:26AM +0200, Kai Krakow wrote:
[...]
Meanwhile, where's a good place to contribute my systemd unit files I
created for different services that not yet seem to be covered by the
systemd distribution? They could also need some review maybe...
Upstream - submit
On 05/06/2013 10:14 PM, Kai Krakow wrote:
Jóhann B. Guðmundsson johan...@gmail.com schrieb:
But now I want to (and need to) give some users cron-like abilities. I
discovered that systemd supports user instances - perfect!
Then install cronie...
That's the obvious solution but a little bit
Hi,
I have noticed sometimes during shutdown, the following message appears
on screen twice:
systemd-cgroups-agent failed to get dbus connection: failed to connect
to socket /org/freedesktop/systemd/private connection refused
The following may be relevant from the logs:
May 07 09:13:05 hobo
'Twas brillig, and Lennart Poettering at 07/05/13 01:41 did gyre and gimble:
This is probably a good release to synchronize a distribution on. For
example, it is our goal that this is the version we will include in
Fedora 19, more or less.
You said that about 195 and then promptly shipped
On Tue, 07.05.13 06:36, Michael Biebl (mbi...@gmail.com) wrote:
2013/5/7 Lennart Poettering lenn...@poettering.net:
* libsystemd-logind.so gained a new call
sd_get_machine_names() to enumerate running containers and
VMs (currently only supported by very new
On Tue, 07.05.13 09:53, Colin Guthrie (gm...@colin.guthr.ie) wrote:
'Twas brillig, and Lennart Poettering at 07/05/13 01:41 did gyre and gimble:
This is probably a good release to synchronize a distribution on. For
example, it is our goal that this is the version we will include in
On 05/07/2013 08:53 AM, Colin Guthrie wrote:
'Twas brillig, and Lennart Poettering at 07/05/13 01:41 did gyre and gimble:
This is probably a good release to synchronize a distribution on. For
example, it is our goal that this is the version we will include in
Fedora 19, more or less.
You said
Hi,
No worries. Maybe you want to add systemd-journal-flush.service to
man systemd-journald.
Maybe altering the help text as following too:
To make the data persistent it is sufficient to create /var/log/journal/
where systemd-journald-flush.service will then store the data.
On Mon, May 6,
Signed-off-by: Karol Lewandowski k.lewando...@samsung.com
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index 49103da..256c813 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -984,8 +984,9 @@
may be used to check whether the given
On Tue, 07.05.13 13:21, Karol Lewandowski (k.lewando...@samsung.com) wrote:
Heya,
Hmm, does that directory always exist? Or only if AppArmor is actually
runtime enabled?
I.e. this check should ideally only return true if SMACK is not only
built into the kernel, but actually really enabled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Really would like to be able to track an alert back to the causing pid.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
This makes ctrl-alt-del reboots more robust, just like systemctl
reboot.
---
src/core/manager.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/manager.c b/src/core/manager.c
index c7f8f20..0508628 100644
--- a/src/core/manager.c
+++ b/src/core/manager.c
@@ -1372,7
On Tue, May 7, 2013 at 2:04 PM, Daniel J Walsh dwa...@redhat.com wrote:
Really would like to be able to track an alert back to the causing pid.
You mean the:
* introduce generic AUGMENT_PID=, AUGMENT_DEVICE= fields
item in the TODO list, right?
A facility that one process can submit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/07/2013 08:22 AM, Kay Sievers wrote:
On Tue, May 7, 2013 at 2:04 PM, Daniel J Walsh dwa...@redhat.com wrote:
Really would like to be able to track an alert back to the causing pid.
You mean the: * introduce generic AUGMENT_PID=,
On 05/07/2013 01:32 PM, Lennart Poettering wrote:
On Tue, 07.05.13 13:21, Karol Lewandowski (k.lewando...@samsung.com) wrote:
Heya,
Hmm, does that directory always exist? Or only if AppArmor is actually
runtime enabled?
/sys/fs/smackfs is only registered when smack lsm is actually
Kok, Auke-jan H auke-jan.h@intel.com schrieb:
[Service]
User=%I
PAMName=systemd-shared
^^ this line is the cause of your problems, as the
/etc/pam.d/systemd-shared file does not exist.
I thought this is virtually profided by pam_systemd.so? But I may try your
suggestion.
Regards,
Jóhann B. Guðmundsson johan...@gmail.com schrieb:
But now I want to (and need to) give some users cron-like abilities. I
discovered that systemd supports user instances - perfect!
Then install cronie...
That's the obvious solution but a little bit counter-productive with
respect to my
Well, actually the timers are a nice benefit only. We want to control user-
initiated background-services for a web application server with this and
cron hasn't been our best friend for this in the past.
David Strauss da...@davidstrauss.net schrieb:
I don't recommend spawning user instances of
On Tue, May 7, 2013 at 4:01 AM, Cristian Rodríguez
crrodrig...@opensuse.org wrote:
El 05/05/13 13:17, Sébastien Luttringer escribió:
Hello,
journcalctl --no-pager or journalctl | cat produce enless content
by looping accross journal entries. The date in lines restart from the
beginning when
20 matches
Mail list logo
