• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 663
  • Last Modified:

Error applying attributes to the file.

Running RHEL 4 / SAMBA 3.0.10 on my server. I set up several unix users added shares, smb.conf looks good. Created two groups users and pca. Added users to samba with full access. The issue, user(s) log on from XP home workstation, shares map fine. All users can create folders add, delete files, no problem. However, the first user I setup can change attributes on files (read-only, hidden, archive), all others users cannot change attributes, "An error occurred applying attributes to the file". I have compared the users until I'm blue in the face and see no differences, except the unix user id values (500-508).

Any suggestions. Thanks.
0
headjava
Asked:
headjava
  • 2
1 Solution
 
ravenplCommented:
> except the unix user id values (500-508).
Well this is importand. Make samba force the user on created files

[share]
        comment = SHARE
        path = /...
        valid users = @special_share_group
        force user = special_share_owner
        force group = special_share_group
        read only = No
0
 
headjavaAuthor Commented:
Thank you for the reply. I'm very new to linux. I did determine the user that creates or copies the file to my RHEL server is who can change attributes (owner). Not clear on the force user option in smb.conf. Would this still only allow the special_share_owner to change attributes ? How would the special_share_owner be different than all other users ?
Its like I need to have an anonymous user and use that user as the special_share_owner.

Thanks for your help.
0
 
ravenplCommented:
The idea of 'force user' is that anybody who is allowed to access this share(valid users) will act as forced user/group and not the real connected user.
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now