<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar/33142127?origin\x3dhttp://fishyweb.blogspot.com', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe", messageHandlersFilter: gapi.iframes.CROSS_ORIGIN_IFRAMES_FILTER, messageHandlers: { 'blogger-ping': function() {} } }); } }); </script>

file permissions, rm & the sticky bit of permission...

Learning :

puzzling over the failure of rm command over a file with rw-rw-rw perms in the /tmp directory.
file was created by user-x group-x
file was being deleted by user-y group-y
the removal should have worked fine with the file perms. alas! rm -rf ended up throwing a permission denied error.
after breaking heads for awhile found the root cause and the solution :)

the issue was caused by the sticky bit set on the /tmp directory - which prevented any deletions of the file other than the owner.
thanks to -
http://docsrv.sco.com:507/en/OSAdminG/ssC.stickydirs.html
http://linuxnorthwest.com/info/linux-file-permission-confusion/

removed the sticky bit from /tmp folder permissions and voila - things worked as expected!

You can leave your response or bookmark this post to del.icio.us by using the links below.
Comment | Bookmark | Go to end