With systemd 218 and 219, I have a strange issue that processes running as
root cannot acquire realtime priority (SCHED_RR, priority 22). Further, if
(and only if) root is logged in (via tty or ssh), users processes can also
not acquire realtime priority. If root is NOT logged in, user processes CA
On Sat, Mar 07, 2015 at 06:11:32PM +0300, Ivan Shapovalov wrote:
> This is needed to interoperate firstboot and sysusers. The former one is
> started
> first, and it writes only /etc/shadow when it is told to set the root
> password.
> It's better to relax checks here than to duplicate functional
On 2015-03-07 at 15:01 +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Mar 05, 2015 at 09:42:17PM +0300, Ivan Shapovalov wrote:
> > On 2015-03-05 at 19:16 +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Thu, Mar 05, 2015 at 09:09:54PM +0300, Ivan Shapovalov wrote:
> > > > On 2015-02-26 at 02
This is needed to interoperate firstboot and sysusers. The former one is started
first, and it writes only /etc/shadow when it is told to set the root password.
It's better to relax checks here than to duplicate functionality in firstboot.
---
v2: rebased on top of master
src/sysusers/sysusers.c
On Thu, Feb 26, 2015 at 02:46:25AM +0300, Ivan Shapovalov wrote:
> This is needed to interoperate firstboot and sysusers. The former one is
> started
> first, and it writes only /etc/shadow when it is told to set the root
> password.
> It's better to relax checks here than to duplicate functional
On Thu, Feb 26, 2015 at 02:46:24AM +0300, Ivan Shapovalov wrote:
> ---
> src/firstboot/firstboot.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://l
On Thu, Mar 05, 2015 at 09:42:17PM +0300, Ivan Shapovalov wrote:
> On 2015-03-05 at 19:16 +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Thu, Mar 05, 2015 at 09:09:54PM +0300, Ivan Shapovalov wrote:
> > > On 2015-02-26 at 02:53 +0300, Ivan Shapovalov wrote:
> > > > On 2015-02-26 at 02:46 +0300, I
On Sat, Mar 07, 2015 at 01:43:32AM -0800, Shawn Landden wrote:
> it is trivial to fall back to our own timestamp
>
> v2: use now()
> v3: remove useless if ()
> v4: add comment
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedeskt
2015-03-06 17:09 GMT+01:00 Didier Roche :
> Le 06/03/2015 16:17, Michael Biebl a écrit :
>>
>> 2015-03-06 11:20 GMT+01:00 Didier Roche :
>>>
>>> It seems like tmp.mount unit was skipped as nothing declared any explicit
>>> dependency against it. What seems to confirm this is that if I add any
>>> e
it is trivial to fall back to our own timestamp
v2: use now()
v3: remove useless if ()
v4: add comment
---
src/timedate/timedated.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/timedate/timedated.c b/src/timedate/timedated.c
index 88d57e9..97b535f 100644
--- a/s
it is trivial to fall back to our own timestamp
v2: use now()
v3: remove useless if ()
---
src/timedate/timedated.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/timedate/timedated.c b/src/timedate/timedated.c
index 88d57e9..b8c586c 100644
--- a/src/timedate/timedate
Hi,
Lennart Poettering:
> Not sure I understand, but there's already --network-bridge= where you
> can configure a bridge that the container's veth link should be added to?
>
The problem is (or was, last time I looked at that option) that
--network-bridge= can only be used once, which is not suf
Hi Ragnar,
I found out and published answer on your Github bug tracker
https://github.com/rthomsen/kcmsystemd/issues/17 .
It seems as simple a using Qt's buitlin "QDBusConnection::sessionBus()"
(qdbusviewer does that).
Alexandre
Le samedi 7 mars 2015, 08:45:42 Mantas Mikulėnas a écrit :
> On
13 matches
Mail list logo
