----- Original Message -----
> ----- Original Message -----
> > On Wed, 2012-11-21 at 21:45 -0500, Nathan Scott wrote:
> > ...
> > > That doesn't make sense to me (nor do I see how chown on the
> > > pmlogger directory changes this behaviour) - the permissions
> > > of a symlink are irrelevant - as described here...
> > > http://superuser.com/questions/303040/how-do-file-permissions-apply-to-symlinks
> > >
> > > Which suggests its the directory... hmmm... the only thing I
> > > can think of is a kernel issue. ...
> >
> > Nod.
> >
>
> Also "lsattr -d <dir>" might show some unexpected attribute?
> Can't think what attribute might cause this behaviour though.
>
> Otherwise maybe some selinux or other security module coming
> into play? (guessing wildly)
And since its so reproducible - strace will probably show EPERM
on a particular syscall, and if its still a mystery after that,
systemtap traces in fs/namei.c::*permission() might be the go -
starting to get in pretty deep though!
cheers.
--
Nathan
|