[systemd-devel] ERRNO parameter in NOTIFY_SOCKET (request for patch review)

[Miguel Angel Ajo Pelayo]

Perfect,

Lennart, thank you very much for the feedback, I'll modify the patch
to do it that way, and I'll send it to the list.

Best,
Miguel Ángel

----- Original Message -----
> On Thu, 03.07.14 05:38, Miguel Angel Ajo Pelayo (mangelajo at redhat.com) wrote:
> 
> > 
> > 
> >   I was trying to make use of the ERRNO message in the NOTIFY_SOCKET
> > mechanism, to signal services that were running on degraded mode
> > but didn't exit.
> > 
> > I discovered that it wasn't implemented [1], so I wrote
> > a patch [2]
> 
> Idea is good!
> 
> I'd prefer if we could handle this similar to how we handle the status
> text string that can be sent via the socket.
> 
> i.e. introduce a new dbus property "StatusErrNo", place it next to the
> existing "StatusText", and call the field in the C "Service" struct
> "status_errno", and put it next to "status_text", and so on...
> 
> Thanks!
> 
> Lennart
> 
> --
> Lennart Poettering, Red Hat
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>