On 04/17/2014 02:28 PM, Matthew Miller wrote:
On Thu, Apr 17, 2014 at 02:07:33PM -0400, Robert Moskowitz wrote:
So for a number of versions, 'service' has been a front end to
'systemctl'. I have a service I am testing the Host Identity
Protocol, and the HIPL implementation: http://infrahip.hiit.fi/ that
is still built around 'service'. And they maintain binaries for a
number of distros, including Centos that do not yet (if ever?) use
'systemctl'.
CentOS 7 will be based on RHEL 7, which includes systemd and therefore
systemctl.
Important to know, but I will have to support Centos 6 for a while, even
if Centos 7 were to come out tomorrow.
Well the HIPL developers are looking into supporting systemctl
method, but for the present, I need the start not to take so long
(and I am talking minutes here, not a few extra seconds until the
failed message).
So is there some option I could use in 'systemctl start
hipfw.service' that will cut down the start time, even if there are
some warnings?
I don't think so. 'system' isn't doing anything special -- it is just
calling systemctl. It looks like the service itself is having some problem
starting up, and that's where the problem needs to be fixed...
Running
systemctl start hipfw.service
runs for minutes before it comes back with the failed message, even
though hipfw is up and running.
So my question is, is there some option I can add that will result in a
much shorter startup time, given the current coding for hipfw (and hipd).
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
