[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

gedit ownership problem

Sticky bit not set :

drwxrwxrwx    5 xma      xma          4096 Feb  8 11:23 TESTFILE


-----Original Message-----
From: redhat-list-bounces redhat com
[mailto:redhat-list-bounces redhat com] On Behalf Of Jack Challen
Sent: Thursday, February 09, 2006 3:31 AM
To: General Red Hat Linux discussion list
Subject: Re: gedit ownership problem

Sorry, replying to the reply -- seem to have lost the original mail

> Yard, John wrote:
>> When using gedit, I have users who cannot edit a file owned by
>> another user, even if the linux permissions
>> allow them ( say even 777 ).
>> What is the circumvention of this problem ?

Are you sure that they can't _edit_ that file? It's possible they can 
edit it (try with another program), but they can't remove it. If that's 
the case, I would think the parent directory has the sticky bit set. (Is

the file in question in /tmp?) Here's the relevant portion from "man

   The  name  of  the `sticky bit' derives from the original meaning: 
keep program text on swap device.  These days, when set for a directory,

  it means  that  only the owner of the file and the owner of that 
directory may remove the file from that directory.  (This  is  commonly 
  used  on directories like /tmp that have general write permission.)


Jack Challen
Technical Consultant, OCSL.

redhat-list mailing list
unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]