Hi Michael,
thank you for your report and your help to make Ubuntu better!
I wanted to recreate but for me nothing of that happened.
$ /etc/init.d/xinetd status
xinetd start/running, process 10735
This never gets any longer.
$ service xinetd status
does just the same.
Also the file "/var/run/xinetd.dump" is not created on my disk.
Never the less I see the code in the init script.
But it seems not to be executed in my case, so lets find why it is in your case.
After the env var init the script sources the common functions via
. /lib/lsb/init-functions
In there it checks for hooks and next sources
. /lib/lsb/init-functions.d/01-upstart-lsb
This then effectively runs "initctl status xinetd" outputs that and exits.
Thereby the critical code is never reached.
Now this is all in the shadow of SysV -> Upstart -> Systemd migrations.
You are reporting on Trusty so you should be on upstart just as my test env.
I wonder how you got to the faulty case there.
Would you mind adding "set -x" to the top of /etc/init.d/xinetd and then
report the output of "/etc/init.d/xinetd status" here?
Also are there any known modifications to affect what I outlined above
in your case?
** Changed in: xinetd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678191
Title:
xinetd service status script appends to /var/run/xinetd.dump with no
rotation mechanism
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/1678191/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
