From user-return-3125-archive-asf-public=cust-asf.ponee.io@guacamole.apache.org Fri Jan 19 20:29:19 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 0D316180607 for ; Fri, 19 Jan 2018 20:29:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id F13A3160C36; Fri, 19 Jan 2018 19:29:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4309B160C1B for ; Fri, 19 Jan 2018 20:29:18 +0100 (CET) Received: (qmail 75775 invoked by uid 500); 19 Jan 2018 19:29:17 -0000 Mailing-List: contact user-help@guacamole.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.apache.org Delivered-To: mailing list user@guacamole.apache.org Received: (qmail 75765 invoked by uid 99); 19 Jan 2018 19:29:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jan 2018 19:29:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C7406C114F for ; Fri, 19 Jan 2018 19:29:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.99 X-Spam-Level: ** X-Spam-Status: No, score=2.99 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id NlDwXTyS0oYH for ; Fri, 19 Jan 2018 19:29:14 +0000 (UTC) Received: from srvmdom1.simard.ca (montreal.simard.ca [206.162.148.138]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 194465F295 for ; Fri, 19 Jan 2018 19:29:14 +0000 (UTC) To: user@guacamole.incubator.apache.org MIME-Version: 1.0 Subject: GUACAMOLE-335 GUACAMOLE_HOME changes X-KeepSent: 9C0111A5:08CACCF8-8525821A:006A267E; type=4; name=$KeepSent X-Mailer: IBM Notes Release 9.0.1 October 14, 2013 Message-ID: From: DMoscovitch@simard.ca Date: Fri, 19 Jan 2018 14:29:08 -0500 X-MIMETrack: Serialize by Router on SRVMDOM1/Simtran(Release 9.0.1FP3|January 12, 2015) at 01/19/2018 02:29:15 PM, Serialize complete at 01/19/2018 02:29:15 PM Content-Type: multipart/alternative; boundary="=_alternative 006B09618525821A_=" This is a multipart message in MIME format. --=_alternative 006B09618525821A_= Content-Type: text/plain; charset="US-ASCII" Hi for 0.9.14 i see changes to GUACAMOLE_HOME as per GUACAMOLE-335 what happens in the case of an upgrade from .9.13 to .9.14 when, .guacamole exists in the tomcat folder , example, /usr/share/tomcat7/.guacamole/ . which holds /extensions and /lib but whre the guacamole.proterties file is symlinked to /etc/guacamole/guacamole.properties it seems in this system the GUACAMOLE_HOME would really be /usr/share/tomcat7/.guacamole/ , but after the upgrade it would assume /etc/guacamole , since it exists. Funny enough the Docs , at least for me, confusingly say the same "Creating a directory named .guacamole, within the home directory of the user running the servlet container. This directory will automatically be used for GUACAMOLE_HOME if it exists. " which I , in .14, took to mean 'home directory' would be like /home/USER... , but as it was the same in the older .13 it seems to mean the folder, like where tomcat would be installed. so, would an upgrade in this case break the system? In retrospect now I think it should be ok right? /danielm --=_alternative 006B09618525821A_= Content-Type: text/html; charset="US-ASCII" Hi

for 0.9.14 i see changes to GUACAMOLE_HOME as per GUACAMOLE-335

what happens in the case of an upgrade from .9.13 to .9.14 when,

 .guacamole exists in the tomcat folder , example, /usr/share/tomcat7/.guacamole/  .
which holds /extensions and /lib but whre the guacamole.proterties file is symlinked to /etc/guacamole/guacamole.properties

it seems in this system  the GUACAMOLE_HOME would really be  /usr/share/tomcat7/.guacamole/ , but after the upgrade it would assume /etc/guacamole , since it exists.

Funny enough the Docs , at least for me, confusingly say the same
"Creating a directory named .guacamole, within the home directory of the user running the servlet container. This directory will automatically be used for GUACAMOLE_HOME if it exists. "
which I , in .14, took to mean 'home directory' would be like /home/USER... , but as it was the same in the older .13 it seems to mean the folder, like where tomcat would be installed.

so, would an upgrade in this case break the system? In retrospect now I think it should be ok right?


/danielm --=_alternative 006B09618525821A_=--