Hello,
I've a very weird behaviour with systemd 217:
# systemctl show -p Wants multi-user.target | grep network.service
# systemctl show -p Wants runlevel3.target | grep network.service
Wants= ... network.service ...
# systemctl show -p Wants multi-user.target | grep network.service
Wants=... net
On Thu, Dec 4, 2014 at 7:06 PM, arnaud gaboury wrote:
> On Thu, Dec 4, 2014 at 4:20 PM, arnaud gaboury
> wrote:
>>>
>>> You seem to be using some mechanism for starting 'systemd --user' that
>>> gives it a DBUS_SESSION_BUS_ADDRESS that assumes dbus-daemon is being
>>> started via a specific thir
When dbus client connects to systemd-bus-proxyd through
Unix domain socket proxy takes client's smack label and sets for itself.
It is done before and independent of dropping privileges.
The reason of such soluton is fact that tests of access rights
performed by lsm may take place inside kernel,
On Mon, Dec 08, 2014 at 08:10:08PM +0100, Lennart Poettering wrote:
> Any idea when you intend to realease this new API in a release or even
> in a stable one?
I'd like to have v2.26-rc1 this month.
Karel
--
Karel Zak
http://karelzak.blogspot.com
___
Hello,
what is the difference between emergency, rescue and single-user?
On F21, systemd-216-12.fc21.x86_64, they all boot into something that
presents itself as "Welcome to emergency mode!" and they all require a
root password. In case of booting into emergency.target, I can see
"Starting Emergen
If a unit is set property by "systemctl set-property", a new dropin
file is generated. But the unit's dropin_paths and dropin_mtime are
not updated. So the unit is shown as need daemon reload.
Update unit dropin_paths and dropin_mtime also when dropin file is
written.
---
src/core/unit.c | 21
On Tue, Dec 9, 2014 at 2:43 PM, Jan Synáček wrote:
> Hello,
>
> what is the difference between emergency, rescue and single-user?
> On F21, systemd-216-12.fc21.x86_64, they all boot into something that
> presents itself as "Welcome to emergency mode!" and they all require a
> root password. In ca
On Tue, 09.12.14 13:43, Jan Synáček (jsyna...@redhat.com) wrote:
> Hello,
>
> what is the difference between emergency, rescue and single-user?
> On F21, systemd-216-12.fc21.x86_64, they all boot into something that
> presents itself as "Welcome to emergency mode!" and they all require a
> root p
On Tue, 09.12.14 11:19, Francis Moreau (francis.m...@gmail.com) wrote:
> Hello,
>
> I've a very weird behaviour with systemd 217:
>
> # systemctl show -p Wants multi-user.target | grep network.service
> # systemctl show -p Wants runlevel3.target | grep network.service
> Wants= ... network.servic
Hi.
Currently notify socket is unavailable in chrooted services (again)
unless you bind mount it there. Is there perhaps another, less
cumbersome way?
So far notify socket was:
1. abstract socket
commit 8c47c7325fa1ab72febf807f8831ff24c75fbf45
notify: add minimal readiness/status protocol
Hello Lennart,
Thanks for answering !
On 12/09/2014 02:10 PM, Lennart Poettering wrote:
> On Tue, 09.12.14 11:19, Francis Moreau (francis.m...@gmail.com) wrote:
>
>> Hello,
>>
>> I've a very weird behaviour with systemd 217:
>>
>> # systemctl show -p Wants multi-user.target | grep network.servic
On Tue, 09.12.14 16:24, Krzysztof Kotlenga (k.kotle...@sims.pl) wrote:
> Hi.
>
> Currently notify socket is unavailable in chrooted services (again)
> unless you bind mount it there. Is there perhaps another, less
> cumbersome way?
>
> So far notify socket was:
> 1. abstract socket
>
>commi
On Tue, 09.12.14 16:07, WaLyong Cho (walyong@samsung.com) wrote:
> Support timer options --on-active=, --on-boot=, --on-startup=,
> --on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
> corresponding with OnActiveSec=, OnBootSec=, OnStartupSec=,
> OnUnitActiveSec=, OnUnitInact
On Tue, 09.12.14 21:46, WaLyong Cho (walyong@samsung.com) wrote:
> If a unit is set property by "systemctl set-property", a new dropin
> file is generated. But the unit's dropin_paths and dropin_mtime are
> not updated. So the unit is shown as need daemon reload.
> Update unit dropin_paths and
On Tue, 09.12.14 12:17, Przemyslaw Kedzierski (p.kedzier...@samsung.com) wrote:
> When dbus client connects to systemd-bus-proxyd through
> Unix domain socket proxy takes client's smack label and sets for itself.
>
> It is done before and independent of dropping privileges.
>
> The reason of suc
Hi,
There's a routine need to support this scenario: a service runs that can fail
and needs to be restarted.
But if it just keeps failing it doesn't make sense to keep restarting forever,
it's just overhead and the system is stuck. So in that case 1) the service
needs to be left stopped in "fa
On Tue, Dec 9, 2014 at 7:47 PM, Nekrasov, Alexander <
alexander.nekra...@emc.com> wrote:
> Hi,
>
> There’s a routine need to support this scenario: a service runs that can
> fail and needs to be restarted.
>
> But if it just keeps failing it doesn’t make sense to keep restarting
> forever, it’s j
Totally missed those. Thanks. Will OnFailure= be activated when the limit is
hit? The manual only directly describes StartLimitAction= which isn’t exactly
what’s required
From: Mantas Mikulėnas [mailto:graw...@gmail.com]
Sent: Tuesday, December 09, 2014 1:05 PM
To: Nekrasov, Alexander
Cc: syste
On Mon, Nov 3, 2014 at 12:41 PM, Andy Lutomirski wrote:
> On Mon, Nov 3, 2014 at 12:21 PM, Jiri Kosina wrote:
>> On Mon, 3 Nov 2014, David Herrmann wrote:
>>
>>> > Agreed, mostly. My only real concern is that this could be annoying
>>> > for the userspace developers who will need to target Linux
On Tue, 09.12.14 12:30, Karel Zak (k...@redhat.com) wrote:
> On Mon, Dec 08, 2014 at 08:10:08PM +0100, Lennart Poettering wrote:
> > Any idea when you intend to realease this new API in a release or even
> > in a stable one?
>
> I'd like to have v2.26-rc1 this month.
>
Hmm, OK, then I'll relea
On Tuesday 09 December 2014 at 17:25:48, Francis Moreau wrote:
> Hello Lennart,
>
> Thanks for answering !
>
> On 12/09/2014 02:10 PM, Lennart Poettering wrote:
> > On Tue, 09.12.14 11:19, Francis Moreau (francis.m...@gmail.com) wrote:
> >
> >> Hello,
> >>
> >> I've a very weird behaviour with
On Tuesday 09 December 2014 at 13:11:41, Nekrasov, Alexander wrote:
> Totally missed those. Thanks. Will OnFailure= be activated when the limit is
> hit? The manual only directly describes StartLimitAction= which isn’t exactly
> what’s required
OnFailure= will be activated each time the uni
Lennart Poettering writes:
> On Tue, 09.12.14 13:43, Jan Synáček (jsyna...@redhat.com) wrote:
>
>> Hello,
>>
>> what is the difference between emergency, rescue and single-user?
>> On F21, systemd-216-12.fc21.x86_64, they all boot into something that
>> presents itself as "Welcome to emergency mo
Mantas Mikulėnas writes:
> On Tue, Dec 9, 2014 at 2:43 PM, Jan Synáček wrote:
>
>> Hello,
>>
>> what is the difference between emergency, rescue and single-user?
>> On F21, systemd-216-12.fc21.x86_64, they all boot into something that
>> presents itself as "Welcome to emergency mode!" and they al
On 12/10/2014 02:25 AM, Lennart Poettering wrote:
> On Tue, 09.12.14 16:07, WaLyong Cho (walyong@samsung.com) wrote:
>
>> Support timer options --on-active=, --on-boot=, --on-startup=,
>> --on-unit-active=, --on-unit-inactive=, --on-calendar=. Each options
>> corresponding with OnActiveSec=, O
On Thu, Nov 20, 2014 at 9:13 AM, Mantas Mikulėnas wrote:
> ~ I'm also getting this on every reload:
>
> systemd[1]: [/usr/lib/systemd/system/systemd-journald.service:24] Failed
> to parse capability in bounding set, ignoring: CAP_AUDIT_READ
>
> I suppose I can ignore the message. I see that cap_a
Can't get recent systemd-git to build on Arch, likely due to the bus error
changes:
$ make -j1 V=1
make --no-print-directory all-recursive
Making all in .
/bin/sh ./libtool --tag=CC --mode=link gcc -std=gnu99 -pipe -Wall
-Wextra -Wno-inline -Wundef -Wformat=2 -Wformat-security
-Wformat-nonliter
27 matches
Mail list logo
