On Mon, Apr 02, 2012 at 06:42:40PM -0300, Pablo Hess wrote:
> Hello Folks,
> 
>     In an effort to port Spacewalk's sysV init script to the
> all-new-and-shiny systemd, Marcelo Mello and I have created quite a few
> "unit files" (systemd speak for init script).
> 
>     Due to service dependencies, we want to propose a new layout to make
> it compatible with the systemd approach.

[...]

> Current status
> ----------------------------
> 
> Currently, the main spacewalk unit file (spacewalk.target) issues
> start/stop/restart/reload commands to all its dependencies. However,
> spacewalk-tomcat6.service is facing a few issues when stopping:

In the past, we've faced issues with tomcat when starting it -- the
service tomcat6 start would return even if the applications weren't
loaded yet, so any HTTP/ajp request would fail. See the lsof hack in
spacewalk-service. How is this issue addressed in the proposed systemd
approach?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to