On Wed, 31 Mar 2004 rob@xxxxxxxxx wrote:

> This I alluded to when I discussed learning the unix, or QSHELL, way.  The
> unix way will allow you to drill down the various directories.  How to do
> that would be best pointed out by the QSHELL experts on the list.

While not a qshell expert, I do use the unix command line a lot ;)  The
unix way is to control authority based on owner of the file, group that
owns the file, and everyone else.  So lets say you have a directory called
/usr/share/manuals that is owned by user james and group users.  On a real
unix (or linux) system a detailed listing would show the permissions to
look something very much like this:

james@stumpy:~> ls -ld /usr/share/manuals
drwxr-xr-x   22 james    users        4096 Nov 13 11:23
/usr/share/manuals

(that second part should all be one line)

This shows that user james has read, write, and execute (in the case of
directories, execute means you can enter the directory) authority.
Everyone who belongs to group users can read and enter the directory.
Everyone else can read and enter the directory.

Controlling what user joe can do means that I need to know what group joe
is in.  If joe is in group users (and I want to allow everyone else who is
in group users) then I can change the permissions to allow write access to
the group.  If I only want users james and joe to have write access, then
I need to create a new group of which they are the only members and then
make the file owned by that group.

So that was a big long introduction to unix file system authority, which
you may already know and now you're just waiting for me to finally answer
the question.  I included it because it is not clear from the examples
that user joe has ownership of the files in question.  Giving a qshell
answer requires an understanding of how it is designed to work.

Let's assume (!) that user joe own directory manuals and all the files
contained within it, including any subdirectories.  Then the QSH command
to give user joe all write access is:

chmod -R u+w manuals

The '-R' argument makes it recurse through all subdirectories.

> However, CHGAUT OBJ('MANUALS/*') USER(JOE)
> DTAAUT(*RWX/NONE) OBJAUT(*ALL/NONE)
> grants or removes authority for "JOE" on objects
> immediately under "MANUALS", but not "MANUALS" itself.
>
> The second command doesn't affect objects further down
> the path, so to grant authority for objects in a
> folder called "/MANUALS/REDBOOKS", it seems I have to
> issue another CHGAUT for the folder contents.
>
> Is there another type of wildcard to include the
> entire contents of the path in one shot, or am I
> missing something obvious?

James Rich

Zvpebfbsg vf abg gur nafjre.
Zvpebfbsg vf gur dhrfgvba.
AB (be Yvahk) vf gur nafjre.
        -- Gnxra sebz n .fvtangher sebz fbzrbar sebz gur HX, fbhepr haxabja

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.