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 >>> >>> 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. Better to leave the symlink in place and train your eyes to ignore the elogs (something we humans are extremely good at) -- Alan McKinnon [email protected]
