Responses to all your suggestions.

["Hudson, Loren (GE Infra, Aviation, Non-GE, US)" <loren.hudson@xxxxxx>]

All,

 

First of all, thanks for all of your responses.  In fiddling around to answer your questions, it now works!  I don't know how, but it seems to be working as desired.  Thank you all for your help.  Sometimes just the right question has to be asked.

 

To answer your questions:

 

A bit tough to obfuscate.  mygroup is the group that needs access.  Bringing the obfuscation down a level by admitting that there are only two directories, in the path, not three.

drwxr-xr-x  37 root     root        1024 Aug  9 09:52 /path

 

drwxrwx---  14 me  mygroup     1024 Dec 13 16:14 /path/to

-rwxr-x---   1 me  mygroup       65 Dec 13 10:54 myscript.sh

groups user1 --- lists mygroup

groups user2 --- lists mygroup

 

We are running Solaris 8 on our dev box and Solaris 10 on our QA box.  Solaris 8 on our prod box.  (This isn't a production issue, yet, by the way).

 

logging in as user1 and typing id:

uid=17887(user1) gid=20(users) --- users is not the correct group.  mygroup's id 53747.  Here's the line from /etc/group

mygroup::53747:user1, user2

 

There is no /etc/logingroup file

 

I've done some looking around with chown (as I was having an issue with that too) and (apparently) in modern systems, you can't chown your files unless you're root.  However, you can change the group of files you own.  There are two reasons for this.  You could turn on the setuid and give a file to root, which would give you access to /etc/shadow or others.  Also, you could give all your files to another user, filling up their disk quota and freeing up yours.  Since the files are in your /home (or wherever), they may never find the files that are filling up their quota. 

Thanks,

 

Mike Hudson
MDW - 
Military Data Warehouse
Java Developer/Solution Architect
Sogeti 
Consultant
loren.hudson@xxxxxx
Desk: 513-243-3663 
~ Dialcomm: *332-3663
Cell: 513-546-4166