Correction for first mail of this morning :

Resolution :
 sudo chown tomcat7 /var/lib/tomcat7/conf/jmxremote.password

 sudo chmod 600 /var/lib/tomcat7/conf/jmxremote.password
 sudo service tomcat7 restart

(sorry bad copy/paste)

2016-06-27 11:34 GMT+02:00 David_dev Dev <dcpc....@gmail.com>:

> Hi,
>
> I'd prefer not change default config and current install (will need to
> change template, deploy scripts and internal docs to :-( ), and in
> precedent answers someone onawer that's this chown is not recommanded and
> should have been change :
>
>
> "So in my opinion we should stop chowning /etc/tomcat7 completely. If we
> really need to set specific permissions for configuration files, it
> should be done on a case-by-case basis."
>
> And more in the 29 May reply, it seems that this case was answered, but
> maybe applied only to tomcat8 duplicated bug ?
>
> 2016-06-27 10:46 GMT+02:00 Emmanuel Bourg <ebo...@apache.org>:
>
>> Hi David,
>>
>> Did you consider moving the jmxremote.password file out of /etc/tomcat7?
>> This would prevent future updates from messing with your files.
>>
>> Emmanuel Bourg
>>
>>
>
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to