On Tue, 2006-06-27 at 18:34 -0400, Donald H Locker wrote:
> Well, they do inherit these permissions from the underlying shell, it's
> just the one that's running at the time the window manager started. So
> you need to set them very early in the process for them to take effect.
> In my .xinitrc I have a . ${HOME}/.profile as the first line. ...
> Everything else works after that.
Very instructive, Donald, and much appreciated!
However, I'm running the Unbuntu distribution of Debain and don't have
any of those files. I tried putting umask 0007 as the first line
in /etc/login.defs, my .bash_profile and my .bashrc. If I use the
command line to create files and directories I get -rw-rw--- and
drw-rw----. Just what I want. If I start ooffice2 from a command line
and use it to create files and directories, I get the same result!
Good! However, if I start OOo from the gnome menu running metacity as
the window manager and create files and directories, I still get
-rw-r--r-- for files and drwxr-xr-x for directories. :( Any ideas?
> (Yes, I'm using sh; have been for 24
> years and it's a hard habit to break.)
Heck, I'm still using vi! :)
Thanks again for all you help. Bobby
> Donald.
>
> Bobby Sanders wrote:
> > On Tue, 2006-06-27 at 21:20 +0100, Andy Pepperdine wrote:
> >
> >>On Tuesday 27 June 2006 19:50, Bobby Sanders wrote:
> >>
> >>>On Tue, 2006-06-27 at 13:57 +0100, Andy Pepperdine wrote:
> >>>
> >>>>On Tuesday 27 June 2006 12:10, Lee Wiggers wrote:
> >>>>
> >>>>>On Mon, 26 Jun 2006 22:55:41 -0500
> >
> > ..........
> >
> >>>>>>On Monday June 26 2006 03:29 pm, Bobby Sanders wrote:
> >>>>>>
> >>>>>>>>Running Linux. OOo2 ignores the file and directory permissions
> >>>>>>>>as set by my operating system. It just sets them the way it ...
> >
> >
> >>>>>>On Mon, 2006-06-26 at 19:48 -0500, Dan Lewis wrote:
> >>>>>>
> >>>>>>> Would you be more specific as to what you mean by OOo 2.0
> >>>>>>>ignoring the file and directory permissions. We need a specific
> >>>>>>>example. .........
> >
> >
> >>>>>>Bobby Sanders replied
> >>>>>>For user joe, set Joe's umask to 0007 in ~/joe/.bashrc
> >>>>>>Make group, "grp"
> >>>>>>cd /home/joe
> >>>>>>mkdir testdir
> >>>>>>chown joe:grp testdir
> >>>>>>chmod 2770 tesdir
> >>>>>>ls -l yields drwxrws--- joe grp testdir
> >>>>>>cd testdir
> >>>>>>
> >>>>>>Use, vi, nano, emacs, touch whatever to create testfile.
> >>>>>>ls -l yields just what you want, i.e
> >>>>>>-rw-rw---- joe grp testfile
> >>>>>>
> >>>>>>Now open OOo2, create testfile2.odt and save to testdir.
> >>>>>>ls -l yields just what you _don't_ want, i.e.
> >>>>>>-rw-r--r-- joe grp testdir Ughh - terrible.
> >>>>>>
> >>>>>>Using terminal command line mkdir testdir2.
> >>>>>>ls -l yields just what you want, i.e
> >>>>>>drwxrws--- joe grp testdir2
> >>>>>>
> >>>>>>Now use OOo2 to create another directory, say testdir2, under testdir
> >>>>>>
> >>>>>>ls -l yields just what you _don't_ want, i.e.
> >>>>>>drwxr-sr-x. So Ugly!
> >
> >
> > Andy Pepperdine Wrote
> >
> >>>>Assuming that you started OOo from the window manager, it sounds to me
> >>>>like the window manager is not using bash to start the application, and
> >>>>so .bashrc is not being used. Try modifying the command that starts OOo
> >>>>from the window manager, or edit the initial OOo startup script to source
> >>>>.bashrc.
> >>>>
> >>>>I've just tried starting Ooo from the command line after changing umask,
> >>>>and it behaved as required.
> >
> >
> > Bobby Sanders replied:
> >
> >>>Fantastic!!! Works for me! What about you, Lee? Thanks so much.
> >>>Tried modifying the command that starts OOo from the gnome menu. No
> >>>luck. I have no idea how to "edit the initial OOo startup script to
> >>>source .bashrc". Any pointers on this or a script would be greatly
> >>>appreciated. Running Ubuntu Breezy, metacity and gnome.
> >>>
> >>>Thanks sooooo much for the help so far. Hope someone can help keep my
> >>>other users from having to start OOo from a command line. :)
> >
> >
> > Andy Pepperdine replied
> >
> >>On my system, the command to start OOo begins with a 2-line shell script.
> >>What
> >>I suggested was to add into this script the line
> >> . ~/.bashrc
> >>
> >>That would at least be common to everyone on the system, rather than having
> >>to
> >>change all the users' menus.
> >>
> >>To change the window menu, you could try modifying it to:
> >> bash -c '. ~/.bashrc; <existing command> '
> >>
> >>I've just realised that unless bash is invoked as an interactive script (or
> >>with certain parameters), it does not read .bashrc
> >
> >
> > Neither of these suggestions worked for me, although I may not have done
> > exactly what you suggested. I have also note that gedit exhibits the
> > same behavior, i.e. created permissions as expected if started from a
> > command, but not if started from the menu system. So the problem
> > appears to stem from the window manager, metacity in my case, and/or the
> > desktop program, gnome in my case, deciding what permissions the
> > application will set when used. It would some sensible for them to
> > "inherit" these properties from the underlying shell rather than
> > arbitrarily setting them the way it sees fit!
> >
> > Again, many thanks for your help. If anyone understands the reason that
> > things are the way they are or knows how to configure them otherwise, I
> > would really appreciate hearing about it.
> > __
> > Bobby Sanders
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
