> (Note
> that this means systemd --user will only work when run from
> [email protected], as access to the cgroup tree is *not* granted for normal
> sessions directly.)
So, how sessions should work now? Before that I started systemd --user
as main session process, and when it exited, session exited t
On Wed, Jul 10, 2013 at 5:48 PM, Lennart Poettering
wrote:
> On Sat, 06.07.13 01:16, Marc-Antoine Perennou ([email protected])
> wrote:
>
>> When creating the cgroup hierarchy for a user slice,
>> chown this slice to the user uid.
>>
>> Signed-off-by: Marc-Antoine Perennou
>> ---
>> src
On Thu, Jul 11, 2013 at 03:02:44AM +0200, Lennart Poettering wrote:
> On Wed, 10.07.13 02:23, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
>
> > ---
> > Does this description fit the masterplan? What about units that
> > systemd will expose for CPU and BlockIO shares, will they still be
On Wed, 10.07.13 15:44, Shawn ([email protected]) wrote:
> really fix ReUsePort capitalization
I fixed two more cases of "ReUse". Also made the man page compile, fixed
a couple of other things and commited this.
Thanks,
Lennart
--
Lennart Poettering - Red Hat, Inc.
__
On Wed, 10.07.13 02:23, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
> ---
> Does this description fit the masterplan? What about units that
> systemd will expose for CPU and BlockIO shares, will they still be
> 1024 and 1000 based?
Yes, they will.
We probably should split the cgroup s
On Sat, 06.07.13 01:16, Marc-Antoine Perennou ([email protected]) wrote:
> When creating the cgroup hierarchy for a user slice,
> chown this slice to the user uid.
>
> Signed-off-by: Marc-Antoine Perennou
> ---
> src/shared/cgroup-label.c | 8
> 1 file changed, 8 insertions(+)
really fix ReUsePort capitalization
On Wed, Jul 10, 2013 at 3:43 PM, Shawn wrote:
> fixed ReUsePort
>
>
> On Wed, Jul 10, 2013 at 3:42 PM, Shawn wrote:
>
>> The idea (not supported in this patch) is that a service could feed via
>> dbus a systemd.socket of itsself, and when that is activated,
fixed ReUsePort
On Wed, Jul 10, 2013 at 3:42 PM, Shawn wrote:
> The idea (not supported in this patch) is that a service could feed via
> dbus a systemd.socket of itsself, and when that is activated, then close
> its own listen()/bind() and shut down, cleanly waiting for systemd to start
> it u
The idea (not supported in this patch) is that a service could feed via
dbus a systemd.socket of itsself, and when that is activated, then close
its own listen()/bind() and shut down, cleanly waiting for systemd to start
it up again when needed. This could be used by ssh for example, triggered
when
On Tue, Jul 9, 2013 at 1:32 PM, Tomasz Torcz wrote:
> On Tue, Jul 09, 2013 at 01:01:13PM -0700, Shawn wrote:
> > --
>
> How do you envision using this? Does it even make sense with
> systemd-managed sockets?
>
I want systemd to be able to have multiple systemd.socket units attached to
the same
We need to cut down the use of udev rules, and move all hardware
matches to the magnitudes more efficient hardware database. Udev rules
were not meant to carry out huge lists of sequential matches against
hardware IDs, this model just doesn't scale too well.
The keymaps are the first, other users
How I can trigger sleep.target in systemd --user session?
My naive approach was first:
[email protected]
[Unit]
Description=sleep.target of a systemd user session
Before=sleep.target
StopWhenUnneeded=yes
[Service]
Type=oneshot
User=%I
RemainAfterExit=yes
ExecStart=/
Hey all,
I'm starting upgrades to old production servers to newer 64-bit Linux that
runs systemd >= v195.
Serial consoles are always my 1st step. Before upgrade it worked great.
After upgrade, with the new systemd-based config, I'm not having much luck
so far.
I configured the grub conf:
seri
The gnome-ostree build system generates disk images that can be
downloaded directly; there is no installer.
In the old model of "dracut shell script + systemd", systemd's main.c
has:
if (arg_running_as == SYSTEMD_SYSTEM ...) {
...
machine_id_setup();
...
}
So after mounting the rootfs, we'd
On Wed, Jul 10, 2013 at 2:41 PM, Tomasz Sobczyk wrote:
> Hmm, it might be my system configuration or a kernel bug, not systemd.
> The thing is that kernel messages instead of being outputted to
> /dev/console are outputted to the currently active VT.
>
> I use metalog as the syslog and when it's r
Hmm, it might be my system configuration or a kernel bug, not systemd.
The thing is that kernel messages instead of being outputted to
/dev/console are outputted to the currently active VT.
I use metalog as the syslog and when it's run, these messages aren't
outputted to the VT. I saw that journal
On Wed, Jul 10, 2013 at 9:19 AM, Umut Tezduyar wrote:
> ---
> systemd/src/core/service.c | 31 ---
> systemd/src/core/socket.c | 33 -
> systemd/src/core/socket.h |3 ---
> 3 files changed, 32 insertions(+), 35 deletions(-)
>
>
On Wed, Jul 10, 2013 at 12:55 PM, Kay Sievers wrote:
> On Wed, Jul 10, 2013 at 12:30 PM, Umut Tezduyar wrote:
>> On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering
>> wrote:
>
>>> We though about just bumping this globally via sysctl, but we feared
>>> that might not sit well with some folks, as
On Wed, Jul 10, 2013 at 12:30 PM, Umut Tezduyar wrote:
> On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering
> wrote:
>> We though about just bumping this globally via sysctl, but we feared
>> that might not sit well with some folks, as we shouldn't change a global
>> setting just because one use
On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering
wrote:
> On Sun, 07.07.13 19:18, Umut Tezduyar ([email protected]) wrote:
>
>> Hi,
>>
>> I have noticed that if journal fails to send messages to
>> /run/systemd/journal/syslog, it increments a counter and every 30
>> seconds it prints out a messa
Hi,
This patch is in reference to
http://lists.freedesktop.org/archives/systemd-devel/2013-June/011405.html
in case your mail client doesn't group it by the thread. I have tested
it on systemd 204 but patch applies to 205 (not tested).
Thanks
On Wed, Jul 10, 2013 at 9:19 AM, Umut Tezduyar wrote
---
systemd/src/core/service.c | 31 ---
systemd/src/core/socket.c | 33 -
systemd/src/core/socket.h |3 ---
3 files changed, 32 insertions(+), 35 deletions(-)
diff --git a/src/core/service.c b/src/core/service.c
index 3617c24.
22 matches
Mail list logo
