Please refer to bug 8465 Not sure if this is a bug or by design. Discovered during testing that manually starting with # cd /usr/share/jetty # java -jar start.jar starts on what seems to be the default jetty port of 8080. When jetty is started as a service it calls /usr/bin/djetty which is a bash script which sets the port to 8088 instead of 8080. The server can then be found at http://localhost:8088
This should affect Cauldron as well. Also, the jetty package in Mageia 2 creates the jetty user properly such that it can be used to run the service, but the Cauldron package does not, because it sets /sbin/nologin as the shell. This should be reverted so that it uses our macros to create the user. The incorrect change happened here: http://svnweb.mageia.org/packages/cauldron/jetty/current/SPECS/jetty.spec?r1=234252&r2=265352
Whiteboard: (none) => MGA2TOOCC: (none) => luigiwalserVersion: 2 => Cauldron
Also currently the install or update fails if id 110 or gid 110 already exists. it is the only package to force numeric values like that. Is that actually needed?
CC: (none) => pablo
The port 8088 in the script comes from Fedora, but I'm not sure if it's intended or a typo. It'd be nice if D Morgan could check with the maintainers there. The script allows the port to be overridden with an environment variable, but the service file doesn't use an EnvironmentFile, so you don't actually have a way of overriding it. D Morgan, if you ever see this, could you please fix this package to use proper Mageia macros in the scriplets, instead of the Fedora ones it has now?
Whiteboard: MGA2TOO => MGA3TOO, MGA2TOO
Assignee: dmorganec => mageiaCC: (none) => marja11
Closing as old.
Resolution: (none) => OLDStatus: NEW => RESOLVEDCC: (none) => davidwhodgins