The Linux (Samba) new guy

There is a lot here, so please be patient.

I'm taking over the net admin responsiblity for a small company. They
have a network with mainly XP and NT boxes and they have a Red Hat
Linux (Samba) system as a file server. It seems great. The /home
directory on the Linux box is where users store their Word, Excel,
ect. files. The /public directory is where users go to access
department shares. They've also did some network installations where
the data files are stored on the /public/<program> directory. In order
for particular users to have RWX permissions to the /public/<program>
data, the last net admin created a group called managers that has RWX
permission to the /public directory. This seemed fine except that
users in the managers group can change the content to the shared
department documents in the /public directory. They should only be
able to RWX the data within the /public/<program> directory. That is
one problem.

The next problem is that I need to do a network install of a
particular program that requires almost every user to have access to
it. I definately don't want the users to have RWX permissions to the
/public directory. I decided to make a new directory called /QPulse. I
also made a group called qpulse and typed chown .qpulse QPulse at the
command line hoping that I gave the qpulse group ownership of the
QPulse directory. I then started putting users into the qpulse group.
In Samba, I created a share called QPulse and directed it to the
/QPulse directory. Everything seemed great. I could access the data
and run the program. Unfortunately users that aren't in the managers
group can't run it. Any idea what I've done wrong.

Thank in advance,

Mike

On Thu, 31 Jul 2003 at 03:30 GMT, Mike wrote:
>> > The next problem is that I need to do a network install of a
>> > particular program that requires almost every user to have access to
>> > it. I definately don't want the users to have RWX permissions to the
>> > /public directory. I decided to make a new directory called /QPulse. I
>> > also made a group called qpulse and typed chown .qpulse QPulse at the
>> > command line hoping that I gave the qpulse group ownership of the
>> > QPulse directory. I then started putting users into the qpulse group.
>>
>> chown -R root:qpulse /Qpulse will be recursive, chowning the contents of
>> the directory as well.
>
> Juha, I did what you posted and I'm half way there. The managers group
> can't access the QPulse directory anymore, but neither can the qpulse
> group. Anyone have any suggesions on how I get the qpulse group access
> to the QPulse directory. Is there anything I have to do with umask or
> password(s)?

chmod -R g+rwx /QPulse

--
Chris F.A. Johnson http://cfaj.freeshell.org
================================================== =================
My code (if any) in this post is copyright 2003, Chris F.A. Johnson
and may be copied under the terms of the GNU General Public License