On 18.04.19 18:17, Felipe Sateler wrote:
> On Thu, 18 Apr 2019 14:21:09 +0200, Josef Moellers wrote:
>
>> Hi,
>>
>> We're currently working on a bug which afaict is due to a race
>> condition:
>>
>> 1) systemd starts xenstored.service
>> 2) /etc/xen/scripts/launch-xenstore does its work (starts /
On Thu, 18 Apr 2019 14:21:09 +0200, Josef Moellers wrote:
> Hi,
>
> We're currently working on a bug which afaict is due to a race
> condition:
>
> 1) systemd starts xenstored.service
> 2) /etc/xen/scripts/launch-xenstore does its work (starts /usr/lib/xen/
> bin/init-xenstore-domain)
> 3) /etc
On 18.04.19 15:35, Lennart Poettering wrote:
> On Do, 18.04.19 14:21, Josef Moellers (jmoell...@suse.de) wrote:
>
>> Hi,
>>
>> We're currently working on a bug which afaict is due to a race condition:
>>
>> 1) systemd starts xenstored.service
>> 2) /etc/xen/scripts/launch-xenstore does its work (s
On Do, 18.04.19 14:21, Josef Moellers (jmoell...@suse.de) wrote:
> Hi,
>
> We're currently working on a bug which afaict is due to a race condition:
>
> 1) systemd starts xenstored.service
> 2) /etc/xen/scripts/launch-xenstore does its work (starts
> /usr/lib/xen/bin/init-xenstore-domain)
> 3) /et
Hi,
We're currently working on a bug which afaict is due to a race condition:
1) systemd starts xenstored.service
2) /etc/xen/scripts/launch-xenstore does its work (starts
/usr/lib/xen/bin/init-xenstore-domain)
3) /etc/xen/scripts/launch-xenstore runs "systemd-notify --ready"
4) "systemd-notify -
On Mon, 07.07.14 09:51, pradip K (pskoth...@gmail.com) wrote:
> Hi Eelco,
Please dont hijack threads, open your own.
> I am trying implement watchdog feature using sd_notify, could you pls give
> us more details on setting $NOTIFY_SOCKET.
> Like how to create socket and assign to environment NOT
Eelco Dolstra logicblox.com> writes:
>
> Hi all,
>
> I've noticed that the command "systemd-notify --ready" does not work
reliably to
> signal that a service is ready. It works sometimes, but most of the time
you get
> a message like:
>
> systemd[1]: Cannot find unit for notify message of
On Tue, 20.05.14 10:56, Eelco Dolstra (eelco.dols...@logicblox.com) wrote:
>
> Hi,
>
> On 18/05/14 18:54, Lennart Poettering wrote:
>
> > Instead of sending the datagram with our own PID in the ucred field we
> > could simply try to override it with our parent's PID.
>
> This only works if th
Hi,
On 18/05/14 18:54, Lennart Poettering wrote:
> Instead of sending the datagram with our own PID in the ucred field we
> could simply try to override it with our parent's PID.
This only works if the service is running as root, right? But yeah, that's
already an improvement over the current s
On Thu, 24.04.14 23:51, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> On Wed, Apr 23, 2014 at 08:50:34PM +0200, Lennart Poettering wrote:
> > On Wed, 23.04.14 15:15, Eelco Dolstra (eelco.dols...@logicblox.com) wrote:
> >
> > > Hi all,
> > >
> > > I've noticed that the command "syst
On Wed, Apr 23, 2014 at 08:50:34PM +0200, Lennart Poettering wrote:
> On Wed, 23.04.14 15:15, Eelco Dolstra (eelco.dols...@logicblox.com) wrote:
>
> > Hi all,
> >
> > I've noticed that the command "systemd-notify --ready" does not work
> > reliably to
> > signal that a service is ready. It works
On Wed, 23.04.14 15:15, Eelco Dolstra (eelco.dols...@logicblox.com) wrote:
> Hi all,
>
> I've noticed that the command "systemd-notify --ready" does not work reliably
> to
> signal that a service is ready. It works sometimes, but most of the time you
> get
> a message like:
>
> systemd[1]: C
Hi all,
I've noticed that the command "systemd-notify --ready" does not work reliably to
signal that a service is ready. It works sometimes, but most of the time you get
a message like:
systemd[1]: Cannot find unit for notify message of PID 3137.
in the journal, and the service stays in the "a
13 matches
Mail list logo
