From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SYVx7-0007UX-MR for garchives@archives.gentoo.org; Sun, 27 May 2012 05:23:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D7DADE072D; Sun, 27 May 2012 05:23:26 +0000 (UTC) Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 513D8E064F for ; Sun, 27 May 2012 05:22:11 +0000 (UTC) Received: by vcbf1 with SMTP id f1so1254929vcb.40 for ; Sat, 26 May 2012 22:22:10 -0700 (PDT) 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 :content-type:content-transfer-encoding; bh=WILeXr4Mj2L8/BSgnC8P/Hxftf1Z6SOQ4ng7xSNlqYE=; b=yxpiJ1zmu5P2vb2htXTfr9IsV92Es7067koccY9pjz+treW1ifwaaO80YHwFRLywH8 GOU27ID5tB0AP/4ik26K4emfpEasc/pNjug97RpN22ym0n8cA38O2HWOa9/Di7/zvfmD n0dpL4IxwQZLqhyKBE8s1SmSWCLYxxnJHgzy3iJ0Q4c34Bd74HNWwNs9Xe0A3oO4ov8K jShFAubP/WoaIS58VCJyG/IF2Wfq00yJsCFDFnYdDyv4M43mFCmai9caqB34guCz1Y/b bqe6ACHCVMg12szUSgk6QDap2N4yWm1ASKr67to1OCCq57fWeGoYnS7cN5loK43R/amO oXkA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.221.1.80 with SMTP id np16mr4516730vcb.33.1338096130821; Sat, 26 May 2012 22:22:10 -0700 (PDT) Received: by 10.220.119.146 with HTTP; Sat, 26 May 2012 22:22:10 -0700 (PDT) In-Reply-To: <4FC1B2D4.30807@gmail.com> References: <4FC1332A.3040703@gmail.com> <4FC1368E.7080005@gmail.com> <4FC13850.2020802@gmail.com> <20120526214001.0668531f@digimed.co.uk> <4FC15692.9070507@gmail.com> <20120526233444.670274c8@digimed.co.uk> <4FC16492.5020603@gmail.com> <20120527012105.284de0e6@khamul.example.com> <4FC17238.4020605@gmail.com> <4FC19A24.2000103@gmail.com> <4FC1B2D4.30807@gmail.com> Date: Sun, 27 May 2012 05:22:10 +0000 Message-ID: Subject: Re: [gentoo-user] How can I control size of /run (tmpfs)? From: Joshua Murphy To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: e457a1a9-d035-42cc-a01e-1c9649f347b6 X-Archives-Hash: 4ce9fd8646119281b126588c00dd2d44 On Sun, May 27, 2012 at 4:51 AM, Dale wrote: > Joshua Murphy wrote: > > Well, I don't see why not. =C2=A0As you say, lack of a proper clean up af= ter > a bad shutdown can cause problems. =C2=A0Anything in /run would disappear > after a shutdown, clean or not, since it is in tmpfs. =C2=A0 It doesn't s= eem > to use much ram either. =C2=A0I really don't know of a reason why it coul= dn't > be set that way. =C2=A0I'm not the sharpest tool in the shed tho. =C2=A0l= ol > > As for one of us setting it to do that manually, I guess one could do > that. =C2=A0If I recall correctly, /var/lock is *supposed* to be cleaned = up > when booting but that was a good long while ago. =C2=A0This may be someth= ing > the devs are already getting ready for. =C2=A0I get the feeling that they= are > taking what I call baby steps. =C2=A0I noticed a upgrade to baselayout an= d I > think OpenRC as well not long ago. =C2=A0I'm not sure what decided to put > stuff in /run. =C2=A0I would think it would be one of those but it could = be > some other package. =C2=A0I guess udev could be one that could have made = it > as well. =C2=A0It does have a directory in there that has stuff in it. = =C2=A0The > rest are empty. > > I'd wait for a serious guru to reply before changing anything tho, just > to be safe. =C2=A0;-) > > You think being up late at night is bad. =C2=A0You should see me when my = meds > are making me goofy. =C2=A0lol > > Dale > > :-) =C2=A0:-) I would try it right now, but a) the only proper 'desktop' I have running is a windows box, the rest of my systems, netbook, laptops, and servers, are stripped down to the bare essentials and are likely to continue skipping along smoothly for a long while regardless of what I do to them, hardly a useful test for something that could potentially cause catastrophic breakage for more 'normal' systems, and b) if it *did* break, I would dread it as I went about trying to remember my exact steps to get there after I wake up tomorrow, especially with the fact that I'm aiming to head to the office when I wake, rather than toy around with fixing things here at home. Maybe tomorrow evening on a couple systems, if the idea itself doesn't bring about any "don't do this, you'll break " responses between now and then (and, depending on the severity of the potential breakage, may still have to poke it with a stick). --=20 Poison [BLX] Joshua M. Murphy