[ale] Group Rights

[Carl Forsell]

Dow, thanks for your response....

I had already completed these steps and still no go.  I edited the group
file manually, then took out my additions and redid them with YAST and same
results.  Everything I read says this should be working, and it is not.

Below is the log I get from the ftp program... (sanitized slightly)

connecting to xxx.xxx.xxx.xxx:21
Connected to xxx.xxx.xxx.xxx port 21
220 ProFTPD 1.2.0pre9 Server (powered by SuSE Linux) [aaa.aaa.aa.us]
USER bbb
331 Password required for bbb.
PASS (hidden)
230 User bbb logged in.
PWD
257 "/" is current directory.
SYST
215 UNIX Type: L8
Host type (S): UNIX (standard)
PASV
227 Entering Passive Mode (xxx.xxx.xxx.xxx,199).
connecting to xxx.xxx.xxx.xxx:3783
- -
connecting to xxx.xxx.xxx.xxx:3783
Connected to xxx.xxx.xxx.xxx port 3783
LIST
150 Opening ASCII mode data connection for file list
Received 148 bytes in 0.1 secs, (10.00 Kbps), transfer succeeded
226 Transfer complete.
#############################################
### this shows the contents of the users home directory###
#############################################
CDUP
250 CWD command successful.
PWD
257 "/" is current directory.
CDUP
250 CWD command successful.
PWD
257 "/" is current directory.
CWD /usr/local/httpd/htdocs/XXX

####################################
### attempt to change to web site directory###
####################################
]
550 /usr/local/httpd/htdocs/XXX: No such file or directory

The directory does exist and has been set (recursive) to 777. Each of the
directories has between 3 - 5 people in the group - and none of them can see
their directories. (all can see their home directories and no more).

Any further assistance would be greatly appreciated.

Carl

-----Original Message-----
From: Dow Hurst <dhurst at kennesaw.edu>
To: ale at ale.org
To: Carl Forsell <cforsell at roman.net>; ale at ale.org <ale at ale.org>
Date: Tuesday, September 19, 2000 3:14 PM
Subject: Re: [ale] Group Rights


>You need to edit /etc/group to add the users to the specific group that
>owns the web directory of the joint project.  Each user should have
>his/her permissions/ownership set normally for their home directory.
>You should think of the joint web directory as owned by a project leader
>( one of the users) and owned by the special joint group you've
>created.  Now in /etc/group add to the special joint group entry the
>individual group members.  See the man page for the /etc/group file for
>the syntax.  The group permissions on the web directory should allow
>group read write exec, while the files within the directory should have
>group read write permissions.  Hope this helps,
>Dow
>
>PS.  Anyone have a better method to suggest?
>
>Carl Forsell wrote:
>>
>> Good morning all...
>>
>> I have a group of users who all need to be able to FTP into common areas
on
>> a SuSE 6.3 box.  I set up groups and gave the groups all rights to the
>> directories (recursive).  When the users try to ftp in, they can see
their
>> home directories, but when they give the path for their web site
>> directories, they get a "cannot find the directory" message.
>>
>> If I assign their home directory to the web site directory, the problem
goes
>> away... however this has implications for their e-mail. Do I need to edit
>> the password file to add a reference to the group?
>>
>> Thank you in advance for any assistance.
>>
>> --
>> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.
>
>--
>__________________________________________________________
>Dow Hurst                   Office: 770-499-3428
>Systems Support Specialist  Fax:    770-423-6744
>1000 Chastain Rd.
>Chemistry Department SC428  Email:dhurst at kennesaw.edu
>Kennesaw State University         Dow.Hurst at mindspring.com
>Kennesaw, GA 30144
>*********************************
>*Computational Chemistry is fun!*
>*********************************
>--
>To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
body.
>

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.