It seems like an old, old problem with chown has surfaced again. At least, I have the same problem that is described at http://lists.gnu.org/archive/html/bug-fileutils/2000-12/msg00008.html and I did not have it a few months back. Quoting: # ls -l total 4 -rw-r--r-- 1 user1 users 5 Oct 26 14:33 regularfile lrwxrwxrwx 1 user1 users 11 Oct 26 14:34 symlink -> regularfile # chown -v user2 symlink ; ls -l owner of symlink changed to user2 total 4 -rw-r--r-- 1 user1 users 5 Oct 26 14:33 regularfile lrwxrwxrwx 1 user2 users 11 Oct 26 14:34 symlink -> regularfile # chown -v --dereference user2 symlink; ls -l owner of symlink retained as user2 total 4 -rw-r--r-- 1 user1 users 5 Oct 26 14:33 regularfile lrwxrwxrwx 1 user2 users 11 Oct 26 14:34 symlink -> regularfile
Ah, coreutils-5.2.1 is the version.
verified that it's still an issue with coreutils-5.2.1-r3 touch regularfile ln -s regularfile symlink chown bin regularfile symlink ls -l regularfile symlink chown -v root symlink chown -v --dereference root ls -l regularfile symlink
i grabbed a patch from upstream cvs for chown-core.c to fix this ... added to 5.2.1-r4, thanks