From Fedora Project Wiki
m (Talk:Packaging/SysVInitScript moved to Packaging talk:SysVInitScript: Moving Packaging Pages to Packaging Namespace) |
m (Rathann moved page Packaging talk:SysVInitScript to Talk:EPEL:SysVInitScripts: SysV initscripts are still used in EPEL5 and EPEL6, but this page was removed altogether after Fedora moved to SystemD.) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 7: | Line 7: | ||
* : engine used for illustrating init scripts | * : engine used for illustrating init scripts | ||
== compatibility with system-config-services == | |||
It might be useful to say that the init script name should be the same that the service-process name. | |||
I used SqlServ for the init.d-script and SqlServ.py for the service-programm and got freezing problems with system.config.services. | |||
It is not obvious for a newbe to find out that system-config-service can not guess the process name from the init-script name | |||
Latest revision as of 11:24, 9 February 2017
The following metadata was found in MoinMoin that could not be converted
to a useful value in MediaWiki:
- : Source function library.
- : engine used for illustrating init scripts
compatibility with system-config-services
It might be useful to say that the init script name should be the same that the service-process name. I used SqlServ for the init.d-script and SqlServ.py for the service-programm and got freezing problems with system.config.services. It is not obvious for a newbe to find out that system-config-service can not guess the process name from the init-script name