Hello, We have Redhat Enterprise Linux 5.5, with gedit 2.16.0. Been having a problem with gedit changing the owner, group, and privileges of a file once we save it. The file name is “question” and the original permissions were: -rwxrwx--- 1 team8 fvtam 57 Jul 27 14:10 question We’ve gotten three different results after saving depending if 1) one person is logged in directly to the server, 2) one person is logged in remotely, or 3) one person is logged in directly to the server while another person is simultaneously
logged in remotely and the two people are editing and saving the same file. Direct Login: The privileges, owner, group for the file named “question” remained unchanged, which is good. There was a backup file created however, question~, and the privileges were changed from 770 to 640, owner changed to skorupaj, but the group
remained the same. See below. -rwxrwx--- 1 team8 fvtam 57 Jul 29 08:04 question -rw-r----- 1 skorupaj fvtam 57 Jul 29 08:04 question~ Remote Login: For remote login the privileges remained the same at 770 but the owner and the group names were changed. Also no backup copy was made. -rwxrwx--- 1 skorupaj users 57 Jul 29 08:12 question Two-Person Login: Also got different results with two people logging in and making changes to and saving to the same “question” file. skorupaj was logged-in remotely while
porterd was logged in directly on the server. Notice that the privileges were changed from 770 to 644, a backup copy was made, and the owner and group names were also changed.
-rw-r--r-- 1 skorupaj users 57 Jul 27 14:13 question -rw-r--r-- 1 porterd users 57 Jul 27 14:12 question~ Is there a fix for this? Thanks, John This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail. |