FTP showing empty shares.

Question

Hello All.
Im sharing a folder (only as FTP not as SMB or AFP) and setting POSIX for owner 'name' to Read Only, a group 'ftpadmin' to Read & Write (so they can add files) and others to None. ACL is set to 'name' Read Only and 'ftpadmin' Full Control.
When i start the service i can log in (off site) but only get a blank folder with none of the files within.
Any ideas?

Answer 1

No a folder/share called 'user1' is where i am aiming, not 'test'. I no longer see 'that' test folder although ive been messing and deleted all the shortcuts in /Lib/FTPServer/FTProot
So you have the ftp daemon configured for "FTP Root and Share Points"?
No idea by what you mean 'exporting the parent directory'
"Exporting" is slang for how a server makes a file share visible; it's what's underneath all this "shares" stuff. It's a term that's particularly common with NFS shares, and less common with the other sorts of shares.
and SFTP doesnt seem to connect.
sftp requires the same port as ssh. If you can ssh into the box, you should be able to get sftp going. (Server Admin, select the server, and it (ssh) is enabled on the "general" page.)
One thing i have noticed is that the hard drive that the FTP shares are on (its a separate drive) has funny ownerships as follows:
(single head) 'admin account (Me)' - Read & Write
(two heads) 'staff group' - Custom
(single head) 'user2' - Read only
(two heads) 'staff group' - Read & Write
(three heads) 'everyone' - No Access
From that Get Info stuff, one head is the user/owner access, two heads is the group access, and three heads is the other/everybody-else access. I'd have to have a look at the custom stuff for staff to see if that's got the access blocked, but given you have access and anybody configured in the Staff group should be able to access the files involved so long as they're in a share served by ftp.
I usually drop down to the bash shell and have a look at the protection masks and the ownerships. Somewhat perversely, the Get Info stuff can be confusing (to me).
Does the username you're logging into here with ftp have access to the files and shares involved? That's the first test. Try accessing the file(s) involved without having ftp involved.
That would need to be "you" or folks in the staff group.
Anything interesting in the ftp logs?
i believe this has been propagated across the drive.
How do i default this back to a standard set?
Standard set? (I'm not sure that such a construct exists.) As for how I examine and change the ownerships, I use the Unix commands ls, chmod and chown:
ls -alR fileordir
sudo chown -R owner:group fileordir
sudo chmod -R u=rwx,go= fileordir
The first (ls) displays the ownerships and access masks starting at the specified file or directory. The second (chown) sets the owner and group, and the second sets the file to be accessible only to the owner. Here's an example of setting the ownerships (to mine, and with a group setting of Staff), and setting the access rights mask to owner and group (staff) to full access.
$ sudo chown MrHoffman:staff ~/x.pdf
$ sudo chmod gu=rwx,o=r ~/x.pdf
To change everything starting at the specified directory and downward (recursive) I use:
sudo chown -R owner:group fileordir
sudo chmod -R u=rwx,go= fileordir
But you'll need to figure out what the accessing user is before you can be certain if the access is permitted or denied to the specified files and directories.