Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 21597EDFF for ; Mon, 4 Feb 2013 18:56:13 +0000 (UTC) Received: (qmail 42497 invoked by uid 500); 4 Feb 2013 18:56:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 42451 invoked by uid 500); 4 Feb 2013 18:56:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 42443 invoked by uid 99); 4 Feb 2013 18:56:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2013 18:56:13 +0000 Date: Mon, 4 Feb 2013 18:56:12 +0000 (UTC) From: "John Vines (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-1035) Scripts don't deal with empty variables well MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 John Vines created ACCUMULO-1035: ------------------------------------ Summary: Scripts don't deal with empty variables well Key: ACCUMULO-1035 URL: https://issues.apache.org/jira/browse/ACCUMULO-1035 Project: Accumulo Issue Type: Bug Components: scripts Affects Versions: 1.4.2 Reporter: John Vines Assignee: John Vines Fix For: 1.5.0 We do a bit of checking for various variables which come in through different avenues. Occasionally, an odd, but acceptable, configuration can result in an empty variable, which causes scripts to throw errors. Wrapping shell variables in quotations should resolve most of these. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira