Red Hat Bugzilla – Bug 737183
Provide native systemd service file
Last modified: 2015-01-06 15:34:55 EST
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 522394 [details]
Created attachment 522395 [details]
Passes simple telnet test...
[root@valhalla system]# systemctl start git.socket
[root@valhalla system]# systemctl status git.socket
git.socket - Git Activation Socket
Loaded: loaded (/lib/systemd/system/git.socket)
Active: active (listening) since Fri, 09 Sep 2011 19:45:07 +0000; 10s ago
Accepted: 0; Connected: 0
[root@valhalla system]# telnet localhost 9418
Connected to localhost.
Escape character is '^]'.
And note there is still a (tight) window to have this in F16
Created attachment 522535 [details]
Once package and shipped your package should no longer have to depend on xinetd
So, I'm using something very similar here, with the difference that I added "Group=nobody". Quite happy about it, it works nicely.
Johann, what's the point of the "After=local-fs.target"? Isn't that part of the default dependencies?
Chris, any plan to push that to Fedora 18? :)
(In reply to comment #6)
> So, I'm using something very similar here, with the difference that I added
> "Group=nobody". Quite happy about it, it works nicely.
> Johann, what's the point of the "After=local-fs.target"? Isn't that part of
> the default dependencies?.
There are several things that are default now but weren't not hence the unit clean-up process  to get things in sync with upstream.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Created attachment 740488 [details]
Could this happen before Fedora 19?
git-18.104.22.168-2.fc19 has been submitted as an update for Fedora 19.
Just for the record, we'll eventually need to redo this to take older releases into account. We've tried hard to make it easy to build git for EL releases from the current spec files. I've talked to a lot of folks that appreciate this ability (and none who have ever cared about systemd, coincidentally). :)
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing git-22.214.171.124-2.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
After upgrading from F18 to F19, and enabling git.socket, I get the following error when trying to connect from another host.
systemd: git.socket failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument
systemd: Unit git.socket entered failed state.
(In reply to Anthony Messina from comment #14)
> After upgrading from F18 to F19, and enabling git.socket, I get the
> following error when trying to connect from another host.
> systemd: git.socket failed to queue service startup job (Maybe the
> service file is missing or not a template unit?): Invalid argument
> systemd: Unit git.socket entered failed state.
I aplogize, I see that Bug 980574 is filed.
Given that I have left the project and a new individual may or may not continue with systemd integration in the project by submitting new feature following whatever demands FPC and FESCo might have and thus new units in the process I'm closing this and all remaining bugs I had submitted for this particular feature as WONTFIX