Samba problems

[mintydroid]

/subscribes

why it's such a ballache I don't know - worked just fine on Mint 10 (Julia) - cannot get it working on Mint 17

Follow the steps on this thread. I think the folder structure (directories) have changed from the general tutorials. I had to look for locations of .conf files, etc before I edited or viewed them.

 

[ODTech]

/subscribes

why it's such a ballache I don't know - worked just fine on Mint 10 (Julia) - cannot get it working on Mint 17

Post your error logs and samba config and also the location of your share folder and we can go through it.

 

[AfricanTech]

Post your error logs and samba config and also the location of your share folder and we can go through it.

Thanks.

Will do - not a priority atm though.

 

[mintydroid]

Got another query. If I want to add e.g. read only abilities to a user on Samba how do I do I do it? I know I can add the user easily to the .conf file.

The purpose is so that other users are allowed to browse the server and copy but not allowed to move and edit anything.

 

[battletoad]

Got another query. If I want to add e.g. read only abilities to a user on Samba how do I do I do it? I know I can add the user easily to the .conf file.

The purpose is so that other users are allowed to browse the server and copy but not allowed to move and edit anything.

[somepath]
path = /path/to/dir
valid users = user1 user2 ...[I]or[/I]...
force group = @groupname ...[I]i may have this syntax wrong[/I]...
read only = no
...[I]other options[/I]...

Now, set ownership of /path/to/dir as user1:groupname, and permission as say 750 or 640. Then, have "groupname" as one of the groups which user2 belongs to. This means that only user1 can write to that path, but the group, which user2 belongs to, can only read.

If, however, you want a few users to write to that folder, set permissions as 775/664, and add "guest ok = yes" to the samba options for that path.

Keep in mind that samba permissions are subject to the underlying unix permissions and you'll be set.

EDIT: forgot something. If you go down the "force group" route, add the group "groupname" to user1's groups, i.e. usermod -a -G groupname user1

ANOTHER: one last thing (hopefully ), for group writing, use "create mask = 0664". Then group members can write to the same files, i.e. no single user takes ownership of a file, ownership is shared among the group.

 

[mintydroid]

What if I:

1.Create a new second user and add it to "valid user"?

2.And then type in "read list = new secondusername"?

Would that work?

 

[ginggs]

What if I:

1.Create a new second user and add it to "valid user"?

2.And then type in "read list = new secondusername"?

Would that work?

How about making the share:

writeable = no

...then putting only your username in the write list:

write list = rogermoore

...and if you want:

guest ok = yes

Write list overrides writeable.

 

[mintydroid]

How about making the share:

writeable = no

...then putting only your username in the write list:

write list = rogermoore

...and if you want:

guest ok = yes

Write list overrides writeable.

I still want them to access with a password.

 

[ginggs]

I still want them to access with a password.

Then:

guest ok = no

 

[mintydroid]

I've got another question. I want to move my drives into another mint install.

On Samba .conf I've got the user as "microserver" and the drive ownership as "microserver" do I remove the ownership, if so how? Or, do I just sudo chown [username...... again with the new name?