On Tue, Sep 16, 2014 at 09:01:53AM -0500, Valeri Galtsev wrote: > That's an interesting thing. Ideally I would prefer the query command do > exactly what I asked, if I asked about existence of some path, I would > like to check that path and tell me which package brought it to my box. In > an idiotic situation when symlink came with one package and actual file > symlink points to from another, when I query symlink, I'd like to get an > answer about it. Am I missing something? Without looking at the source itself, I can't be sure, but I suspect that 'rpm' first did look for the given path in the RPM database, failed to find anything, and then performed the equivalent of 'readlink -f /etc/httpd/modules/mod_proxy.so', canonicalizing the path, then searching again. I'm not sure what you're describing in your example. RPMs can provide symlinks, and they show up in the package manifest. If a package included a symlink to a directory or file owned by another package, I'm sure that querying the path to the symlink would return the package that includes the symlink, not the package that includes what the link pointed to. -- Jonathan Billings <billings at negate.org>