Am 26.11.2015 um 08:00 schrieb Eduard Bloch: > Package: systemd > Version: 228-2 > > Dear Maintainer, > > * What led up to the situation? > > I created a buggy configuration of apt-cacher-ng and wondered why it did not > start. When I run the service from command line, it dumps a couple of usefull > hints to STDERR. I expected to see this in "systemctl status" output. I saw > only ten lines and this contained only useless cruft, something about > "hold-off time over" etc. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Since I expected useful information to be before this cruft, I used the > -n option as described in the systemctl manpage. -n 20, actually. > > * What was the outcome of this action? > > The same output was displayed. Only 10 lines with useless information. Feels > like -n ... value is simply ignored, I can set -n100 or -n1000, makes no > difference. >
Works here. But I actually need a service which produces more then 10 lines of output when started. Remember that status only shows the logs from the most recent start/stop/restart attempt. I think it would be confusing if it showed output from, say the last boot. For that you need journalctl indeed. And if the daemon itself doesn't log to syslog or stdout, journald obviously doesn't catch that. So from what I can see, there is not really a bug here. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
