Description of problem:
Let's get the ball rolling on this one...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 522810 [details]
Created attachment 522811 [details]
Created attachment 522812 [details]
Created attachment 522813 [details]
Created attachment 522814 [details]
Created attachment 522815 [details]
Once package and shipped your package should no longer have to depend on xinetd
Thanks for working on this. FWIW is this supposed to be obsolete the xinetd support as well? just wonder if I should get rid of the dependency with it or still keep it.
Well you can your component no longer should haver to depend on xinetd since it now ships unit files that do exactly the same thing.
We dont have anykind of policy around migrating from xinetd to systemd but I assume that fpc would be consistent in their work and ask maintainers to package xinetd snippets into an seperated xinet subpackages should they want to continue to ship xinetd snippets as is being done with legacy sysv init scripts.
I also recommend that your rename http unit files to ebhttp to avoid potential conflicts with apache.
Okay, thanks. for renaming, I was about to do that.
One more question though, how can I test this if it works as expected?
I tried to do systemctl enable ndtpd.socket and ndtpd.service though, when connecting to the port 2882, it was just refused. and systemctl status ndtpd.socket gives me failed then. systemctl status ndtpd.service also says failed but there are no logs in /var/log/messages systemd brought up the ndtpd daemon at all.
The testing package is available at http://koji.fedoraproject.org/koji/taskinfo?taskID=3354914
Rereading https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd, and the service file seems missing Wants= line for .socket. however the daemon still not running successfully because of the failure on getpeername().
I'm expecting systemd will invoke the service when the socket is accepted though, as per this behavior, it seems not. any idea to get this working on systemd anyway?
Okay, finally I got it. fixed in 1.0-12.fc18
ebnetd-1.0-12.fc17 has been submitted as an update for Fedora 17.
ebnetd-1.0-12.fc16 has been submitted as an update for Fedora 16.
ebnetd-1.0-12.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ebnetd-1.0-12.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
ebnetd-1.0-12.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
ebnetd-1.0-12.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
ebnetd-1.0-12.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.