Am 10.02.2013 14:14, schrieb Michael Mol: > On Sun, Feb 10, 2013 at 7:40 AM, Alan McKinnon <[email protected]> > wrote: >> On 10/02/2013 13:49, Michael Mol wrote: >>> On Feb 10, 2013 3:29 AM, "Florian Philipp" <[email protected]> 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 >>>>> [...] >>>> 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. >>>> [...] >> >> 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 >
That's odd. Is your system up-to-date and recently rebooted? I'm running most of these services, too. But I have no open files in /var/run. > 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). :) > BTW: Am I the only one annoyed by elog messages like "If you are updating from $ANCIENT_VERSION make sure to change $DEPRECATED_FEATURE" lurking in the tree for years? Especially because when you see the message, it is a pain in the ass to check which version you were actually using before. Regards, Florian Philipp
signature.asc
Description: OpenPGP digital signature
