[Pkg-systemd-maintainers] Bug#738787: systemd: Can't get complete status of xinetd when using systemd

[Salvo Tomaselli]

> Not quite correct. You can either embed or build-depend on
> libsystemd-daemon-dev.
> There is also no runtime dependency on systemd. The sd_notify API
> becomes a NOOP when not run under systemd.
Well but it would have to link against an extra library for nothing then, and 
the call could not be removed by a compiler, unless by doing static linking.

> I guess this is not quite what the sd_notify API is intended for. So I'd
> say, no, what you want is not covered by systemd.
Okay.

Well it's a nice feature to have because when xinetd finds an error in the 
configuration of some service, it will start anyway but not start just that 
particular service, so this is quite useful (it has helped me a few times).

> What you might do is have xinetd log that information to stdout and it
> will show up in the journal and systemctl status as the last 10 lines.
$ wc -l /run/xinetd.dump 
73 /run/xinetd.dump

(yeah I know, it's quite long).

Do you think that adding something like /usr/bin/xinetd-statusdump to print 
that would be a good idea?

I am not much into patching it because upstream is not so active, and 
apparently it would also not solve anything at all.

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
                -- Galileo Galilei

http://ltworf.github.io/ltworf/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140213/2295855f/attachment-0002.sig>