Project

General

Profile

Bug #925

shares generated in smb.conf as writeable=no

Added by sgtfoo about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Medium
Assignee:
Category:
file sharing
Target version:
-
Start date:
06/20/2012
Due date:
% Done:

0%


Description

Wanted to document an issue I hit while connecting to shares from both windows and ubuntu on my HDA.

After going through the permissions checks..

sudo chmod -R 775 /var/hda/files
sudo chown -hR _username_ /var/hda/files

I found that something else was stopping me from adding directories to certain shares. Noticing it was based on shares, it seems there may be a bug in how the Amahi Dashboard builds the smb.conf
I looked at my smb.conf (found at /etc/samba/smb.conf) and it turns out that the problematic shares had the property

writable = no

set to no instead of yes, so I changed it to be

writable = yes

on all my shares and lo and behold, access is as it should be, while still restricted between users.

History

#1 Updated by bigfoot65 almost 9 years ago

Please validate if this bug is still valid. There have been many changes to Amahi for Ubuntu. If it's not valid, please mark as resolved. We will close it after review.

#2 Updated by bigfoot65 over 8 years ago

  • Priority changed from Normal to Medium

#3 Updated by cpg almost 6 years ago

  • Status changed from New to Closed

this was fixed a while ago (and present in the currently available release)

Also available in: Atom