Closed kakawait closed 9 years ago
Good catch. I'll fix that asap. For now you can "copy" the template, fix it by yourself and configure tomcat_server_sysvinit_template
to your (fixed) copy.
Yeah I already did that :) I just create the issue for the community :+1:
Fixed in 1.1.0. I did not integrate any migration code (PID file management).
but if CATALINA_PID
is inside a folder that TOMCAT_USER
does not have write access the startup script will failed. But never mind if it works as default ok, user can plugs it own service template!
Good catch. Tried to use daemon function for that, but daemon does not help. Updating the SysV default service template for various little fixes right now.
Inside Sysvinit system when using an instance user Tomcat process still run under root user.
using
result
Inside
service_sysvinit.j2
there is reference to instance user here https://github.com/silpion/ansible-tomcat/blob/master/templates/service_sysvinit.j2#L11 but it never uses.I'm not Tomcat expert and you may have your reason to keep process on root user but if it just missing we can do something like
(can be improved by adding default value for
tomcat_user_group
)