From owner-freebsd-current@freebsd.org  Tue Jan  5 19:36:59 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6C2CA6341A;
 Tue,  5 Jan 2016 19:36:59 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com
 [IPv6:2607:f8b0:4001:c05::22e])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id A9856111E;
 Tue,  5 Jan 2016 19:36:59 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: by mail-ig0-x22e.google.com with SMTP id z14so14718443igp.0;
 Tue, 05 Jan 2016 11:36:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=pP+evAbr2F18Xf2IgorfUnyR24EFCw6bCJenhyu6puE=;
 b=Wdh9aEq7+1iLm2VeNw6nv3n/k9hFQBk44J7lFSymnc4ESaOx+MbqqcpJJDD96ZhhnP
 WA5g3IZJAGWDBcV7vUMvH68MsDpfAEa081iuYf6hT5WGnUchKooP9BZzC43L1ef9FRD/
 KgMXmjXkdoBmPLEaez+Nt+1H+kMils0wchJZx5PwnrxAyuOEkvNVOBGk7belLHDNUUET
 KMvFjdNzH8FdC82LNy6N4MND+sJbg/jRNNGZDzfq6cwkfMAfSmNnHrZf51SL88/L5ynz
 SXIh5fzZNhzlJLRi3UZWuX2Bd444zsSBRSo9StkYMQrSnszAgZKC5FXHgxxkqr7rlJIp
 eAeA==
MIME-Version: 1.0
X-Received: by 10.50.160.11 with SMTP id xg11mr5355809igb.83.1452022619146;
 Tue, 05 Jan 2016 11:36:59 -0800 (PST)
Received: by 10.107.163.202 with HTTP; Tue, 5 Jan 2016 11:36:59 -0800 (PST)
In-Reply-To: <568B84DC.7080705@FreeBSD.org>
References: <5514E5B0.1030509@rawbw.com> <568B8291.50700@FreeBSD.org>
 <568B84DC.7080705@FreeBSD.org>
Date: Tue, 5 Jan 2016 14:36:59 -0500
Message-ID: <CAFMmRNwS-bKA9P1bbesp08iEBBfzYW5k_EMN7nqeWY=-+f4z6A@mail.gmail.com>
Subject: Re: environment corrupt; missing value for QT_IM_MO
From: Ryan Stone <rysto32@gmail.com>
To: Andriy Gapon <avg@freebsd.org>
Cc: office@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 19:36:59 -0000

On Tue, Jan 5, 2016 at 3:54 AM, Andriy Gapon <avg@freebsd.org> wrote:

> Is there a limit on the environment's size?
>

If memory serves, this is bounded by ARG_MAX in sys/syslimits.h.  The value
is not tunable as far as I know, so if you want to experiment with changing
it you will have to change syslimits.h and recompile your kernel.