HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- wrong protections on new files in Samba Share
Operating System - HP-UX
1833589
Members
4028
Online
110061
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2003 07:51 AM
04-02-2003 07:51 AM
Files being written into a samba share aren't being granted the desired permissions.
The share config is:
[ui]
path = /opt/axiom/workspace
public = yes
guest ok = yes
writeable = yes
write list = pcguest
create mask = 774
force create mode = 774
inherit permissions = yes
Yet the files are created with the incorrect group settings. The settings for Other were corrected after adding the "create mask" directive, but for some reason group still won't go right.
Here's the parent directory permission (for the effect of Inherit Permissions = yes)
# ll -d /opt/axiom/workspace
drwxrwxrwx 3 axadmin axiom 1024 Apr 2 10:26 /opt/axiom/workspace/
# ll /opt/axiom/workspace
total 14
drwxrwxrwx 3 axadmin axiom 1024 Apr 2 10:26 ./
drwxrwxr-x 14 axadmin axiom 1024 Apr 2 10:37 ../
drwxrwxr-x 14 axadmin axiom 1024 Apr 1 16:34 axiom_source/
-rwxrw-r-- 1 pcguest axiom 8 Apr 2 09:59 testfile.txt*
-rwxrw-r-- 1 pcguest axiom 8 Apr 2 10:03 testfile1.txt*
-rwxrw-rw- 1 pcguest axiom 8 Apr 2 10:05 testfile2.txt*
-rwxrw-rw- 1 pcguest axiom 8 Apr 2 10:26 testfile3.txt*
Thanks for any help/information
The share config is:
[ui]
path = /opt/axiom/workspace
public = yes
guest ok = yes
writeable = yes
write list = pcguest
create mask = 774
force create mode = 774
inherit permissions = yes
Yet the files are created with the incorrect group settings. The settings for Other were corrected after adding the "create mask" directive, but for some reason group still won't go right.
Here's the parent directory permission (for the effect of Inherit Permissions = yes)
# ll -d /opt/axiom/workspace
drwxrwxrwx 3 axadmin axiom 1024 Apr 2 10:26 /opt/axiom/workspace/
# ll /opt/axiom/workspace
total 14
drwxrwxrwx 3 axadmin axiom 1024 Apr 2 10:26 ./
drwxrwxr-x 14 axadmin axiom 1024 Apr 2 10:37 ../
drwxrwxr-x 14 axadmin axiom 1024 Apr 1 16:34 axiom_source/
-rwxrw-r-- 1 pcguest axiom 8 Apr 2 09:59 testfile.txt*
-rwxrw-r-- 1 pcguest axiom 8 Apr 2 10:03 testfile1.txt*
-rwxrw-rw- 1 pcguest axiom 8 Apr 2 10:05 testfile2.txt*
-rwxrw-rw- 1 pcguest axiom 8 Apr 2 10:26 testfile3.txt*
Thanks for any help/information
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2003 08:38 AM
04-02-2003 08:38 AM
Solution
Hi Peter,
File permissions are a confusing beast where Samba is concerned!
You may have confused yourself (& Samba) a bit by your config.
The inherit permissions parm will override the create mask and force create mode parms. On top of that the HPUX execute bits are manipulated according to the various map archive, map system, map hidden parms - this allows various functionality from the Win/DOS side.
If you want the file perms to be 774, then just set inherit permissions = no, the rest of your settings are fine. I've just done a quick test on a CIFS/9000 A.01.09.02 server and saved some files from Notepad; their perms are 774 using your settings.
It's worth remembering that the various map settings mentioned above mean that the various permission bits mean something different to the HPUX/DOS machines. Running the command testparm will dump all your current parms from smb.conf, also displaying the default values that you haven't entered into smb.conf.
There's some good reading on permission related parms in the O'Reilly Using Samba book - p140 onwards or within Chapter 5 if you're accessing the book via SWAT. The various parms are also documented in the smb.conf man page, also available via SWAT.
regards,
Darren.
File permissions are a confusing beast where Samba is concerned!
You may have confused yourself (& Samba) a bit by your config.
The inherit permissions parm will override the create mask and force create mode parms. On top of that the HPUX execute bits are manipulated according to the various map archive, map system, map hidden parms - this allows various functionality from the Win/DOS side.
If you want the file perms to be 774, then just set inherit permissions = no, the rest of your settings are fine. I've just done a quick test on a CIFS/9000 A.01.09.02 server and saved some files from Notepad; their perms are 774 using your settings.
It's worth remembering that the various map settings mentioned above mean that the various permission bits mean something different to the HPUX/DOS machines. Running the command testparm will dump all your current parms from smb.conf, also displaying the default values that you haven't entered into smb.conf.
There's some good reading on permission related parms in the O'Reilly Using Samba book - p140 onwards or within Chapter 5 if you're accessing the book via SWAT. The various parms are also documented in the smb.conf man page, also available via SWAT.
regards,
Darren.
Calm down. It's only ones and zeros...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2003 09:32 AM
04-02-2003 09:32 AM
Re: wrong protections on new files in Samba Share
Darren - thanks! taking out the inherit did the trick.
I had read the smb.conf man page -- but as you say it's tricky.
I had read the smb.conf man page -- but as you say it's tricky.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP