"Mike Gerdts" <[EMAIL PROTECTED]> wrote:
> > POSIX allows symlinks to avoid file meta data (i.e. inodes).
> > Solaris implements inodes for symlinks but ignores owner and permissions.
>
> Perhaps I lost sight of my original goal. Since the permissions on a
> symlink really don't matter, perhaps the a -h option on chmod(1)
> doesn't really need to alter a symlink. Ignoring it may be
> sufficient. I'm now thinking that the best fix for 4786969 be to just
> lstat(3C) before chmod(2) and ignore those that are symbolic links.
So what you like is a chmod that includes the secret knowledge tar
has built in?
> Why does this matter? I have had many times in my life as a sysadmin
> where files or directories owned by root got their permissions
> changed. In a number of cases, I checked the helpdesk ticket log and
> found that there were cases along the lines of "Fred no longer works
> here. Please change the ownership of all files in ~fred/project to be
> rw by group freds-old-team and no one else." The action taken by the
> junior admin is "chgrp -Rh freds-old-team ~fred/project; chmod -R
> g+rw,o-rwx ~fred/project". How much damage is done if fred has the
> symbolic links to /etc, /net/server/something, and
> /projects/some-other-projects?
I know these kind of sysadmins :-(
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
