| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Collateral damage in non-root changes |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 22 Nov 2012 03:17:47 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1353566342.4467.5.camel@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
----- 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) cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] Collateral damage in non-root changes, Ken McDonell |
|---|---|
| Next by Date: | Re: [pcp] Collateral damage in non-root changes, Nathan Scott |
| Previous by Thread: | Re: [pcp] Collateral damage in non-root changes, Ken McDonell |
| Next by Thread: | Re: [pcp] Collateral damage in non-root changes, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |