I am able to connect to my Unraid server using filezilla with root or a created user account, I see the disks but the folders are empty. I am able to FTP from other linux machines with know issue. Does any have a reason or better a fix......

 

Thanks...

I'm having the same issue the files are there because I can see them in the windows share, but not able to see them in the ftp.. hmmm...

Anyone know why this is?  I found a few threads on this board regarding this and all are unanswered.  I enabled show hidden files in flashfxp (I saw that somewhere in another post) and perhaps this explains why people are installing another ftp program?  Still being able to write files and not read a directory listing?  I'm very confused...  I played around w/a few other option still nothing and this doesn't seem to be an issue w/vsftpd, but rather some option somewhere (I'm guessing) in Unraid.

 

Nate

Hmmm, okay others on the internet disabled SELinux, but since unraid isn't the standard linux distro install does anyone know where this setting may (or the setting that's causing this issue) be?

 

http://forums.fedoraforum.org/archive/index.php/t-119321.html

Ah okay the i changed the permissions on the directory & files and now it works.

 

Does anyone know how to change the default permissions for files uploaded?

for those that care this is the command I ran

 

chmod -R 666 disk1

 

Then I ran it for disk2 (I only have 2, I'm sure there's a way to string together multiple commands in one, but I'm pretty rusty).  Also, you don't need to do 666, just make sure that the 'other' group has read access.  Search google for linux file permissoins to see how they work if you're new to it.

 

Nate

Does anyone know how to change this so I don't have to run that command after I upload stuff so that it's just 666 by default?  There's a setting somewhere that's setting the permission for no read/write by the owner/other group, and I'm wondering if anyone knows where that is.

 

Nate

I think if you set in your login script, "umask 0111", that should do the trick.

Does anyone know how to change this so I don't have to run that command after I upload stuff so that it's just 666 by default?  There's a setting somewhere that's setting the permission for no read/write by the owner/other group, and I'm wondering if anyone knows where that is.

 

Nate

 

try adding the following line to your /etc/vsftpd.conf file

 

anon_umask=000

 

You will have to do this upon every reboot.

 

 

http://vsftpd.beasts.org/vsftpd_conf.html

 

 

I think if you set in your login script, "umask 0111", that should do the trick.

 

Sorry, I'm horrible at linux - which login script were you suggesting (and where is it?).  I googled around for a bit and tried myself to find something, but came up empty.  Thanks!

I changed local_umask=077 to =000, but after I reboot it goes back to 077 - why is this (after writing and quiting in VI i went back and checked (before reboot) and the change was there - then after reboot it goes back)?  After changing the setting and then uploading a small text file the permissions are -rw------; why is this?

 

When I type umask at my command prompt it is 0022, which if I'm understanding correctly, should create permissions of -rw-r--r--

 

All I want is what I had before (with my w2k3 server) which is all directories and files can be read via ftp by any user w/access.  Right now I'm logging in as root via ftp and can't even see the files on my disk3 unless I do a chmod -R for the whole drive, but then if I upload a new file/directory, I have to run that command again.  I'm trying to make it so all files are -rw-r--r--; except in one directory that I call INCOMING which everyone will have rw-rw-rw- to.

I changed local_umask=077 to =000, but after I reboot it goes back to 077 - why is this (after writing and quiting in VI i went back and checked (before reboot) and the change was there - then after reboot it goes back)?

 

The root filesystem is on a ram drive. When you reboot all changes are lost and it is reloaded from the bzroot file on your flash.

In order to make the changes permanent, you need to add some script lines to your /boot/config/go script

 

Here is an example command.

Test it out, I'm not sure what freshly booted config is.

My unraid has been up for 3 months seeding torrents and I do not want to reboot it.

 

sed -e s#local_umask=.*#local_umask=000#g -i.bak /etc/vsftpd.conf

 

Here is the diffs.

--- /etc/vsftpd.conf.bak        2009-07-28 07:30:53.441016499 -0400

+++ vsftpd.conf 2009-08-12 09:37:52.727013169 -0400

@@ -8,7 +8,7 @@

#

# Allow local users to log in.

local_enable=YES

-local_umask=077

+local_umask=000

# local_umask=000

anon_umask=000

local_root=/mnt

Thanks for your help although I still have been unable to figure out how to modify the script correctly.

 

Even with my umask setting to 000 in vsftpd.conf when I uploaded a small text file the the permissions are -rw------; why is this?  If the default permissions for a text file is 666, why is it not this after upload?  Even if I subtract out the default umask of 022 that means it should be -rw-r--r-- - correct?  Instead it's just -rw-------

 

Very lost sorry.

 

This is my only hiccup w/my unraid server.  How does everyone else share files w/their friends from their server?

 

Nate

Okay so my umask setting in vsftpd.conf is 000 and at a regular command prompt where my umask setting was 022, I changed it to 000.

 

I just uploaded a file as root via ftp and the permissions are -rw-------

 

I'm not worried around making permanent changes to the script so that when I reboot they stick, right now I'm just trying to figure this out!  Right now the only way around this is for me to manually do a chmod after I upload files.

 

Nate

Okay so my umask setting in vsftpd.conf is 000 and at a regular command prompt where my umask setting was 022, I changed it to 000.

 

I just uploaded a file as root via ftp and the permissions are -rw-------

 

I'm not worried around making permanent changes to the script so that when I reboot they stick, right now I'm just trying to figure this out!  Right now the only way around this is for me to manually do a chmod after I upload files.

 

Nate

 

First, i want to mention one thing... in order for you to be able to download the files via ftp, the "world" or other bit much be set to 4 (or 6 or 7). 

 

You could write a script to find the files which have incorrect permissions and have it change them.. something like this:

 find /mnt/user/ -type f -perm -600 ! -perm -004 -exec chmod 666 {} \;

This will find any files that have the permission set for the owner to read and write but does not have the others set to read. (note the chmod 666 could also be 644 or 604, i just used your value from a previous post)

 

Additionally, you may want to think about running the cache_dirs addon if you don't already, I'm not 100% sure, but if you were to write some code which executed this find command every few minutes, you would likely keep you drives from spinning down.  With the cache-dirs addon, the file listing is kept in cache and no need to spin up/stop from spinning down your drives (at least in theory)

 

Cheers,

Matt

Thanks for the tip!  Although, I'm confused as to what must be set to 4, 6 or 7?

 

First, i want to mention one thing... in order for you to be able to download the files via ftp, the "world" or other bit much be set to 4 (or 6 or 7).

 

Sorry for needing clarification - thanks again.

 

Nate

Thanks for the tip!  Although, I'm confused as to what must be set to 4, 6 or 7?

 

First, i want to mention one thing... in order for you to be able to download the files via ftp, the "world" or other bit much be set to 4 (or 6 or 7).

 

Sorry for needing clarification - thanks again.

 

Nate

 

The "world" or other bit must be changed to 4(read) 6(read and write) ir 7(read, write, execute).  The "world" or other bit is the last of the three numbers.

 

a permission of 644 means the following:

6-owner can read and write

4-group can read, but cannot write

4-everyone who is not the owner and not in the group the file belongs to can read it, but not write to it

 

Hope this helps clear things up.

 

Cheers,

Matt