On 1/15/2014 11:46 AM, Bush, Eddie wrote:
> Great feedback, Mark! Thanks!
>
> As this will be for a single app, I'm not concerned with having quite as
> complex of a setup as you do. The box does not seem to have selinux enabled:
>
> [ebush@tuldgskap01 ~]$ selinuxenabled
> [ebush@tuldgskap01 ~]$ echo $?
> 1
>
> Is there something that would cause the script to be successfully invocable
> interactively and yet make it fail at boot? I'm thinking the answer is yes,
> based off of what I'm seeing. Perhaps sudo doesn't like being run by root?
>
> Since I'll lead the dev team, I'll have teeth to make sure the app does not
> misbehave. I can't imagine why one would, as I've never had issues before. I
> suppose, if requests were still processing, a problem could occur. However,
> we'll use F5 and drain-stop the node prior to performing maintenance, so ...
> I'm going to take a simpler path than you've advocated but keep your thoughts
> around in case I do experience an issue :-)
>
> I'll look into a more formal daemon mechanism. I think commons-daemon comes
> with tomcat. I'm trying to avoid many manual pieces like that, but working
> (and I define working as "it comes up after boot") is not optional!
>
> Thanks again! ... and thanks to the others who have provided feedback too! It
> is very much appreciated! My take-away: there's a standard way to launch a
> daemon, and you should be doing that!
>
> Eddie
>
Hi, Eddie-
It's been a while but one script I used had the following start line:
daemon --user ${tomcat_user} ${tomcat_script} start ${tomcat_start_opts}
where daemon was a function defined in init.d/functions. Within daemon,
runuser was used to execute the startup script.
-Terence Bandoian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
