Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B86C610237 for ; Wed, 21 Jan 2015 19:36:46 +0000 (UTC) Received: (qmail 52130 invoked by uid 500); 21 Jan 2015 19:36:46 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 52101 invoked by uid 500); 21 Jan 2015 19:36:46 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 52091 invoked by uid 99); 21 Jan 2015 19:36:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2015 19:36:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yusaku@hortonworks.com designates 209.85.217.170 as permitted sender) Received: from [209.85.217.170] (HELO mail-lb0-f170.google.com) (209.85.217.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2015 19:36:21 +0000 Received: by mail-lb0-f170.google.com with SMTP id w7so2391669lbi.1 for ; Wed, 21 Jan 2015 11:36:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=4WSdt58tDBsMCofdHyKtjwzs1HjNKUYk2weWrrWvmN4=; b=Gs/JG6nUqMq+ambK0sDuZT2LPVR+9JsI6pm6VXGZr1H0JDR69BiGe8sz8FbX0kiJZX aDgHSmVyCUSD2GFy790gs0nAohD8275eyIF0RJMXrQO4uAKqM8O5iItA7AoDNK/Ldxdo cRQaI7eAaGqQw9I21bKL//7inqOJzsXU38jPoQsvkhFkfVcnqERPEsJIcwvfU5NjoLYB PWs1zBlRCuU1D2h15Xq3CtxRy8yXUSrVhouTTcQMXMmgNqPLEkuGsCDlW93hWLynMvJ5 qQZYdU8uoGIa4/Ta+D5vcu1avnelJik/utAMzGMKVlXvIgDfqoNSozgaCZSrCkyqsJBg vP7w== X-Gm-Message-State: ALoCoQlpWQrLcnQUyxilfe1CjH07kcMwIrKnlp6w6/3aCdd+OcjaUHAJFsEiM8BLkluWVI8dA5E5FRsgj40S9047CUvtN/LLt0ct7bZ2V3I/nRCDT7dUIYg= MIME-Version: 1.0 X-Received: by 10.152.42.164 with SMTP id p4mr39630135lal.45.1421868979866; Wed, 21 Jan 2015 11:36:19 -0800 (PST) Received: by 10.112.189.6 with HTTP; Wed, 21 Jan 2015 11:36:19 -0800 (PST) In-Reply-To: References: <16edaa6c.123af.14b0c0926f3.Coremail.liulu-xyz@163.com> Date: Wed, 21 Jan 2015 11:36:19 -0800 Message-ID: Subject: Re: Config the directory from ambari web From: Yusaku Sako To: "user@ambari.apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Looks like this was introduced via https://issues.apache.org/jira/browse/AMBARI-4162. Ambari should not disallow directories like /home/... from being used in config properties if the user wishes. I think the intent was to not include /home as one of the mount points to be considered when making default recommendations for config properties related to directories. Liulu, do you want to go ahead and file a bug for that? Thanks, Yusaku On Wed, Jan 21, 2015 at 11:22 AM, jun aoki wrote: > Good point. It seems the check comes from here > https://github.com/apache/ambari/blob/trunk/ambari-web/app/models/service= _config.js#L963 > > Does anyone know why this restriction is taken place? > > On Wed, Jan 21, 2015 at 2:28 AM, =E5=88=98=E7=A6=84 w= rote: >> >> Hello. >> >> Why ambari consider the directory "Can't start with home(s)"? >> >> I want to set the directory to be like =E2=80=9C/home/xxx/dir=E2=80=9D, = but ambari >> refuses. >> >> I think directory can be any dir that user want. >> >> >> -- >> liulu >> >> > > > > -- > -jun --=20 CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to= =20 which it is addressed and may contain information that is confidential,=20 privileged and exempt from disclosure under applicable law. If the reader= =20 of this message is not the intended recipient, you are hereby notified that= =20 any printing, copying, dissemination, distribution, disclosure or=20 forwarding of this communication is strictly prohibited. If you have=20 received this communication in error, please contact the sender immediately= =20 and delete it from your system. Thank You.