Re: systemd vice SysV/LSB init systems - what next ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/19/2011 07:51 PM, Alexander Kurtakov wrote:
FWIW, tomcat package (note the missing 6) is at version 7.x.y and ships with 
the systemd integration and seems to be working fine.

Alexander Kurtakov

If you are speaking of this then that fails to meet the packaging guidelines...
[Unit]
Description=Release implementation for Servlet 3.0 and JSP 2.2
After=syslog.target network.target

[Service]
Type=forking
PIDFile=/var/run/tomcat.pid
EnvironmentFile=/etc/sysconfig/tomcat
ExecStart=/etc/init.d/tomcat start <-- this kinda is a hack and does not meet the packaing guidelines
ExecStop=/etc/init.d/tomcat stop <-- this kinda is a hack and does not meet the packaing guidelines

[Install]
WantedBy=multi-user.target

"Packages
 may also provide a SysV initscript file, but are not required to do so.
 This format is considered legacy, but Fedora still contains init 
mechanisms such as upstart which do not support the systemd unit file 
format. If present, the SysV initscript(s) must go into an optional 
subpackage, so as not to confuse sysadmins. The guidelines for SysV 
initscripts can be found here: Packaging:SysVInitScript"

So there is a question if we cant properly convert it..

JBG
Note.png
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux