Summary: | www-servers/tomcat - add xinetd config file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | vltg0903 |
Component: | New packages | Assignee: | William L. Thomson Jr. (RETIRED) <wltjr> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | java |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | tomcat config for /etc/xinetd.d |
Description
vltg0903
2006-12-22 02:49:35 UTC
Created attachment 104565 [details]
tomcat config for /etc/xinetd.d
I don't think I will ever by default provide a xinetd.d script for Tomcat. Not sure I have seen many invoke Tomcat that way. Pretty sure it's not one of the ways upstream recommends starting Tomcat. To address the unprivileged port issue, I was planning on modifying the init script to use jsvc. Since upstream does provided examples on how to start Tomcat that way. So I would assume it's more recommended. There is not eta for jsvc support, and another bug has been open requesting that for some time. Inclined to mark this as wontfix, but will ponder it for a bit. Give those that would want to use xinetd, are likely familiar with it. Making their own xinetd service file, is kinda moot. I don't want to start tomcat with xinetd, I just want to use xinetd for port forwarding. Ok that's not going to happen. You might want to use xinetd, someone else might prefer to use iptables, and someone else might do it another way. So if the only reason if for port forwarding, then that will have to be done on an individual basis, their preferred way. It's not as if I'm proposing to introduce a xinetd dependency, or even installing the file with 'disable = no'. But if that is you last word, oh well, then so be it. Yeah sorry, not trying to be rude. Just can't do everything to please everyone all the time. At some point once we do finally provide an option to use jsvc to start Tomcat. Having anything do port re-direction will be kinda moot. |