I did this and I still have the problem.  This is only with SO and only
with files created and saved in one place and then opened and saved to
the share_dir.

[EMAIL PROTECTED] wrote:
> 
> Janyne,
> 
> You need to change the permissions on the shared directory.
> Add the SETGID bit to it.
> 
> You can do this with:
> 
>     chmod g+s share_dir
> 
> And, make sure that the group id on the directory is staff.
> Do this:
> 
>     chgrp staff share_dir
> 
> Then, any files that get created in that directory by ANY user
> and ANY program will have a group of 'staff'.
> 
> That should help,
> 
> Jim McQuillan
> [EMAIL PROTECTED]
> 
> On Thu, 20 Jun 2002, Janyne Kizer wrote:
> 
> > I don't think that I explained the problem correctly.  All of the users
> > have their UPG and many of them are also in a "staff" group.  Members of
> > the "staff" group have a shared directory.  When people save files from
> > vi, pico, nedit, gimp, etc. to the shared directory, the group is set to
> > shared just as it should be.  If they save the file to their home
> > directory, the group is set to their UPG.  If they open FILE1.TXT from
> > their home directory, edit it and then decide to save it to the shared
> > directory, FILE1.TXT is given the "staff" group as it should be --
> > UNLESS the file was opened from their home directory with SO an then
> > saved to the shared directory.  In that particular case, the file has
> > the same settings as it did in the home directory.
> >
> > Note the test_after.doc file below.  It was created with SO and saved in
> > my home directory.  It was then reopened and edited and then saved to
> > the shared directory.
> >
> > -rw-rw-r--    1 wkme    staff          63 Jun 20 14:05 nedit2test
> > -rw-rw-r--    1 wed23   staff          39 Mar 28 08:06 newfile.txt
> > -rw-rw-r--    1 ets     staff          15 Mar 29 14:11 test2.doc
> > -rw-rw-r--    1 wkme    wkme         7680 Jun 20 14:16 test_after.doc
> > -rw-rw-r--    1 wkme    staff        2551 Jun 20 13:46 testing123.jpg
> >
> >
> >
> > Ken Barber wrote:
> > >
> > > The User Private Groups (UPG) scheme is unique to Red Hat, and IMO is a bit
> > > ridiculous.  I've never used them.
> > >
> > > It has been my practice to create groups that actually do something useful,
> > > such as "faculty", "students", "finaid" and so on.
> > >
> > > Ken Barber
> > >
> > > On Thursday 20 June 2002 11:08 am, Janyne Kizer wrote:
> > > > I am using RH 7.2 and SO 5.2.   We have a shared directory set up for
> > > > people to use
> > > > (http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/ref-guide/s1-users
> > > >-groups-private-groups.html). When someone saves a SO file into there home
> > > > directory, edits that file and then saves it to the shared directory, the
> > > > permissions are the same as on the file in their home directory.  All other
> > > > programs seem to work fine (Gimp, Nedit, etc.) but StarOffice insist on
> > > > keeping the group the UPG.  ARG!  Any suggestions?
> > >
> > > --
> > > "Rule by pressure groups is merely the prelude, the social conditioning for
> > > mob rule."
> > >         -- Ayn Rand, "The New Left: The Anti-Industrial Revolution"
> >
> >
> 
> --

-- 
Janyne Kizer
CNE-3, CNE-4, CNE-5
Systems Programmer Administrator I
NC State University, College of Agriculture & Life Sciences
Extension and Administrative Technology Services


-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to