On Fri, 2008-04-04 at 08:27 -0700, Bruce Hyatt wrote: > > > I carelessly executed "chmod 666 ///" from a terminal as su > > > in a user account. > > --- Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > > Possibly all he needs to get X going is 'chmod +t /tmp'. > > I tried this first and it didn't work. > > > On Thu, 2008-04-03 at 13:12 -0400, Andrew Parker wrote: > > > > > > rpm -qa | xargs rpm ----setperms --setugids > > This returned "----setperms: unknown option" > So I tried it using "--setperms" and it returned > "chmod: invalid mode string: '[various 7-digit numbers]'" > It seemed to be looping through this with different 7 digit > numbers coming back. The mode string indicates how to set the > permissions. > > How would chmod interpret ///? All files and directories 3 > layers deep? In a Unix (and Linux) pathname any sequence of one or more / characters collapses into a single /. Thus /// is exactly the same as / so your chmod affects only files in the root directory (and not those beneath it). Which is why I thought /tmp might the cause of the problem. poc
