On Wed, Dec 17, 2014 at 4:34 AM, jenia.ivlev wrote:
>
> Hello.
>
> I want to start synapse (its a program that allows to run programs more
> easily) at login using systemd. So I created this systemd-service config
> file:
>
> [Unit]
> Description=Syanpse start up
> After=lxdm.service
>
On Tue, Dec 16, 2014 at 06:06:41PM +0100, Ken Werner wrote:
> From: Ken Werner
>
> Since the order of the first and second arguments of the raw clone() system
> call is reversed on s390 and cris it needs to be invoked differently.
Applied.
Zbyszek
___
Hello.
I want to start synapse (its a program that allows to run programs more
easily) at login using systemd. So I created this systemd-service config file:
[Unit]
Description=Syanpse start up
After=lxdm.service
[Service]
User=jenia
ExecStart=/usr/bin/synapse
[Inst
On Tue, Dec 16, 2014 at 09:58:39PM +0100, Umut Tezduyar Lindskog wrote:
> ---
> src/shared/path-util.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/shared/path-util.c b/src/shared/path-util.c
> index dcc8321..304281f 100644
> --- a/src/shared/path-util.c
> +++ b/sr
On Wed, Dec 10, 2014 at 4:11 AM, Lennart Poettering
wrote:
> In fact, I think we should drop the
> libcap dependency altogether and just do the two syscalls it offers to
> us natively in systemd code. Neither is libcap a particularly nice
> library, nor is the stuff it does particularly complex, h
On Tue, Dec 16, 2014 at 04:10:44PM -0600, Benjamin Marzinski wrote:
> On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke wrote:
> > Hi all,
> >
> > in commit 3ebdb81ef088afd3b4c72b516beb5610f8c93a0d
> > (udev: serialize/synchronize block device event handling with file
> > locks) udev start
On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke wrote:
> Hi all,
>
> in commit 3ebdb81ef088afd3b4c72b516beb5610f8c93a0d
> (udev: serialize/synchronize block device event handling with file
> locks) udev started using flock() on the device node, supposedly to
> synchronize with an ominous
---
src/shared/path-util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/shared/path-util.c b/src/shared/path-util.c
index dcc8321..304281f 100644
--- a/src/shared/path-util.c
+++ b/src/shared/path-util.c
@@ -518,7 +518,7 @@ fallback:
if (r < 0)
On 12/16/2014 03:54 PM, Umut Tezduyar Lindskog wrote:
Hi,
Is there a reason why systemd-modules-load is loading modules
sequentially? Few things can happen simultaneously like resolving the
symbols etc. Seems like modules_mutex is common on module loads which
gets locked up on few occasions thr
On 2014-12-10 22:37, Lennart Poettering wrote:
> On Tue, 09.12.14 18:26, Lennart Poettering (lenn...@poettering.net) wrote:
>
> Przemyslaw,
>
>>> +++ b/units/u...@.service.m4.in
>>> @@ -0,0 +1,23 @@
>>> +# This file is part of systemd.
>>> +#
>>> +# systemd is free software; you can redistribut
From: Ken Werner
Since the order of the first and second arguments of the raw clone() system
call is reversed on s390 and cris it needs to be invoked differently.
Signed-off-by: Ken Werner
---
src/nspawn/nspawn.c |6 +++---
src/shared/missing.h | 10 ++
2 files changed, 13 inser
On Tue, Dec 16, 2014 at 5:15 PM, Rauta, Alin wrote:
> Sorry, "between systemd restarts".
Right. That's what I thought. In that case I would not worry about it
for now, as explained previously, and rather handle it together with
the flushing of addresses and routes when we get to that.
Cheers,
On Tue, 2014-12-16 at 08:45 +0100, David Herrmann wrote:
> Hi
>
> On Mon, Dec 15, 2014 at 9:20 PM, Dan Williams wrote:
> > On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
> >> systemd tries to launch logind service which now waits for services it
> >> is ordered After and eventually ti
On 12/15/2014 06:27 PM, Lennart Poettering wrote:
On Mon, 15.12.14 08:01, Ken Werner (k...@linux.vnet.ibm.com) wrote:
From: Ken Werner
Since the order of the first and second arguments of the raw clone()
system call is reversed on s390 and cris it needs to be invoked differently.
Signed-off-
Sorry, "between systemd restarts".
/Alin
-Original Message-
From: Tom Gundersen [mailto:t...@jklm.no]
Sent: Tuesday, December 16, 2014 3:56 PM
To: Rauta, Alin
Cc: Lennart Poettering; systemd Mailing List; Kinsella, Ray
Subject: Re: [systemd-devel] [PATCH v2] Add FDB support
On Tue, Dec
On Tue, Dec 16, 2014 at 4:59 PM, Tom Gundersen wrote:
> On Tue, Dec 16, 2014 at 4:54 PM, Umut Tezduyar Lindskog
> wrote:
>> The other thought is, what is the preferred way of loading modules
>> when they are needed.
>
> Rely on kernel autoloading. Not all modules support that yet, but most
> do.
On Tue, Dec 16, 2014 at 4:54 PM, Umut Tezduyar Lindskog
wrote:
> The other thought is, what is the preferred way of loading modules
> when they are needed.
Rely on kernel autoloading. Not all modules support that yet, but most
do. What do you have in mind?
> Do they have to be loaded on ExecStar
On Tue, Dec 16, 2014 at 4:28 PM, Rauta, Alin wrote:
> Regarding the flushing of entries that's done because we don't want to have
> dangling configuration between system restarts,
You mean these settings are remembered by the hardware between reboots?
Cheers,
Tom
__
Hi,
Is there a reason why systemd-modules-load is loading modules
sequentially? Few things can happen simultaneously like resolving the
symbols etc. Seems like modules_mutex is common on module loads which
gets locked up on few occasions throughout the execution of
sys_init_module.
The other thou
Hi Tom,
Thanks for your feedback. I will change "VLAN" to "VLANId" in the next patch.
Regarding the flushing of entries that's done because we don't want to have
dangling configuration between system restarts, but currently the discussion is
ongoing internally and it may take some time.
Best
For the reference, -flto option was preventing static linker from
making the assignments. Could be very well something specific to our
toolchain.
On Fri, Dec 12, 2014 at 11:50 PM, Umut Tezduyar Lindskog
wrote:
> On Fri, Dec 12, 2014 at 4:46 PM, Lennart Poettering
> wrote:
>> On Fri, 12.12.14 10:
> On Tuesday, 16 December 2014 10:41 AM, P J P wrote:
>> and now after 6-7 hours suddenly I see the login prompt with kernel-3.18.0.
>> I have hit
>> # shutdown -r now
>> and boot-up has stalled at the same spot again. Let's see...
>
> I've restarted it with
>- systemd.log_level=debug syste
Hi
It's much simpler that you simply add a neat comment in that bug report
and or sane upstream that you tested what Zbyszek proposed and it
worked, rather than sending mail to 4 individuals and two mailinglist
and at the same time leave out that information from the bug report
where this all
23 matches
Mail list logo