This bug was fixed in the package tomcat6 - 6.0.24-2ubuntu1.1
---
tomcat6 (6.0.24-2ubuntu1.1) lucid-proposed; urgency=low
* debian/patches/fix-jsp-regression.patch: Fix regression in JSP compilation
that resulted in Duplicate local variable errors when using Struts 1.2
or
** Tags added: verification-done
** Tags removed: verification-needed
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in
As far as I can tell, this is now working okay. I haven't been able to
test a package upgrade, but have tried installing a new package with and
without /etc/default/tomcat6 already existing and with/without
TOMCAT6_[USER|GROUP] being set and all seems well. If the tomcat6 user
and group are
@Max: could you enable lucid-proposed and confirm that the problem is
satisfactorily fixed in the tomcat6 6.0.24-2ubuntu1.1 package ? Thanks
in advance.
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification
** Branch linked: lp:ubuntu/lucid-proposed/tomcat6
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
This bug was fixed in the package tomcat6 - 6.0.26-2
---
tomcat6 (6.0.26-2) unstable; urgency=low
* debian/tomcat6.{postinst,prerm}: Respect TOMCAT6_USER and TOMCAT6_GROUP
as defined in /etc/default/tomcat6 when setting directory permissions and
authbind configuration
** Branch linked: lp:ubuntu/tomcat6
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
Ubuntu-server-bugs
Accepted tomcat6 into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
** Changed in: tomcat6 (Debian)
Status: New = Fix Released
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in
** Branch linked: lp:debian/sid/tomcat6
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
Ubuntu-server-bugs
** Also affects: tomcat6 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: tomcat6 (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: tomcat6 (Ubuntu Lucid)
Status: New = In Progress
** Changed in: tomcat6 (Ubuntu Lucid)
Assignee: (unassigned) =
** Branch linked: lp:~ttx/tomcat6/lucid-sru
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
** Description changed:
Binary package hint: tomcat6
I run tomcat6 on Ubuntu 8.10, installed from the tomcat6 package. I
need to run tomcat as a different user to 'tomcat6' so have configured
this via the TOMCAT6_USER variable in /etc/default/tomcat6. I then
manually changed the
** Changed in: tomcat6 (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: tomcat6 (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification
It sounds like either 2 or 3 would 'fix' the bug. Solution two strikes
me as the simplest from the end-user perspective, and has the added
advantage that it would allow future package updates to tweak
permissions.
--
tomcat6 package should fully support running as a different user
Yes, I'll go for (2) in Lucid SRU and for (2)+(4) for Maverick (see
https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-tomcat for
details). Thanks for your input !
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received
There are several solutions:
1/ Only set the permissions on original installation (do not modify on upgrades)
2/ Make installation/upgrades look into /etc/default/tomcat6 to get the user
name
3/ Make installation/upgrades respect dpkg-statoverride (do not change
permissions on upgrades if
** Summary changed:
- tomcat6 does not respect dpkg-statoverride settings
+ tomcat6 package should fully support running as a different user
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you
You are only testing /etc/tomcat6/. This is not in the list of files
that the package is modifying. See comment 2 in this bug or the
package's postinst script.
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug
Sorry about that. Confirmed.
--
tomcat6 package should fully support running as a different user
https://bugs.launchpad.net/bugs/557300
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
Ubuntu-server-bugs mailing
I agree with that statement. The current version of tomcat6 correctly
supports two modes of operation: running as a system instance as the
tomcat6 user (package tomcat6) or running as a private instance
under the user of your choice (package tomcat6-user, then use tomcat6
-instance-create).
21 matches
Mail list logo
