From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 641A7138970 for ; Sun, 10 Feb 2013 15:29:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EA20E21C0D2; Sun, 10 Feb 2013 15:29:16 +0000 (UTC) Received: from s-out-001.smtp25.com (s-out-001.smtp25.com [67.228.91.90]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 35C1321C0C0 for ; Sun, 10 Feb 2013 15:29:14 +0000 (UTC) Received: from ccs.covici.com (ccs.covici.com [70.109.53.110]) by s-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id r1AFTCoB026405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sun, 10 Feb 2013 10:29:13 -0500 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.6/8.14.5) with ESMTP id r1AFTCFi021472 for ; Sun, 10 Feb 2013 10:29:12 -0500 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] What to do with /var/run? In-reply-to: References: <51175A29.3090002@binarywings.net> <51179534.4080308@gmail.com> Comments: In-reply-to Michael Mol message dated "Sun, 10 Feb 2013 08:14:30 -0500." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.4.2 Date: Sun, 10 Feb 2013 10:29:12 -0500 Message-ID: <21471.1360510152@ccs.covici.com> From: covici@ccs.covici.com X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: s-out-001.smtp25.com-r1AFTCoB026405 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 X-Archives-Salt: 61e7d86b-b349-419b-b3a5-f5fabaccbeaf X-Archives-Hash: d3bbe7690eac66861534fcaa490e0e64 Michael Mol wrote: > On Sun, Feb 10, 2013 at 7:40 AM, Alan McKinnon wrote: > > On 10/02/2013 13:49, Michael Mol wrote: > >> On Feb 10, 2013 3:29 AM, "Florian Philipp" wrote: > >>> > >>> Am 10.02.2013 06:11, schrieb Grant: > >>>> I received the following ELOG message after an emerge: > >>>> > >>>> * One or more symlinks to directories have been preserved in order to > >>>> * ensure that files installed via these symlinks remain accessible. > >> This > >>>> * indicates that the mentioned symlink(s) may be obsolete remnants of > >> an > >>>> * old install, and it may be appropriate to replace a given symlink > >> with > >>>> * the directory that it points to. > >>>> * > >>>> * /var/run > >>>> > >>>> Should I change anything? > >>>> > >>>> - Grant > >>>> > >>> > >>> If my understanding of the situation is correct, we see this message > >>> whenever a package is updated that in the old version installed to > >>> /var/run and now has migrated to /run. > >>> > >>> Even if I'm wrong, there is nothing to be done. /var/run is intended to > >>> be a symlink to /run. If it is, then all is fine. > >>> > >>> Regards, > >>> Florian Philipp > >>> > >>> > >> > >> Except we'll be seeing that elog to the end of time > >> > >> "lsof -n |grep /var/run" will tell you what, if anything running, is using > >> that symlink. > >> > > > > It's probably better to leave the symlink in place for now. What happens > > when the user installs a package they have never had before and that > > package uses /var/run? > > > > It will make a directory which isn't what you want. > > Hm. > > lsof -n|grep /var/run|cut -d\ -f1|sort -u > > gives me > > acpid > avahi-dae > bluetooth > cupsd > dbus-daem > gdm > syslog-ng > > Of those, at least avahi and cups are emitting /var/run elogs, which > tells me they're defaulting to using /var/run instead of /run, if > /var/run is present. > > Obviously, the transition isn't finished yet...software should default > to /run rather than /var/run, or the symlink can never be known to be > safe to remove on a given system. > > > Better to leave the > > symlink in place and train your eyes to ignore the elogs (something we > > humans are extremely good at) > > Oh god no...Then you end up like some folks who get bit every time > something changes (despite being warned about it for a months in > advance). :) > I had to actually prevent the migration to /run by changing the boot.misc script because if I do not do that, a number of subdirectories which I had created in /var/run were not in /run and a number of apps would not start properly and indeed it is not taking much space, so I am not sure why anyone bothered. The only other option would have been to write something to fix the /run, but that was not what I wanted to do. /var/lock had this same problem also. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com