On Tue, 2012-02-28 at 21:19 -0600, David Lambert wrote:
> I have got a little further in diagnosing this "memory leak" of
> systemd-journal. It appears to worsen when I have a process that emits
> data to stdout. I presume that systemd-journal is attempting to put this
> somewhere but failing, a
I have got a little further in diagnosing this "memory leak" of
systemd-journal. It appears to worsen when I have a process that emits
data to stdout. I presume that systemd-journal is attempting to put this
somewhere but failing, and consequently is buffering it in its own
process. Where is th
Please excuse if this is trivial, but I am a systemd newbie.
I am running systemd on Angstrom/Beaglebone. After a couple of days I
notice that the process systemd-journald had grown and was ultimately
killed by the kernel's OOM handler. I investigated the
systemd-journald.conf file which stated
Running systemd-nspawn on a Linux kernel compiled without
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
fails with the cryptic error message
clone() failed: Invalid argument
Give user a more helpful error message when clone() fails
Signed-off-b
Hi
I tried as well the following configuration. My script shall be
started before ANY other service is shut down.
Stopping a virtual machine is only one example. Synchronizing data
into a truecrypt container another.
[Unit]
Description=my shutdown ser
'Twas brillig, and Léo Gillot-Lamure at 28/02/12 02:38 did gyre and gimble:
> Hi.
>
> I investigated a bit about creating an equivalent of ck-launch-session
> (i'm interested about this because it would be possible for tmux to
> create a logind session for each tmux session), and it appears
> impo
Le mardi 28 février 2012 à 00:52 +, Colin Guthrie a écrit :
> Hi,
>
> I'm getting bug reports about startx not registering user sessions under
> systemd.
>
> With console-kit, ck-xinit-session did the job and I was hoping someone
> (Fred - maybe you've done it on SuSE?) had written the equiv
