Where to set share-specific settings?
BeHau
12 Posts
March 18, 2022, 9:40 amQuote from BeHau on March 18, 2022, 9:40 amHello,
we use PetaSAN for CIFS and i wonder how to set different settings for some shares.
Example here would be having set "access based share enum = Yes" on some shares but not all.
I understand one could set those settings in CIFS-Settings\Share Secure but this applies to all shares in that case.
Any hints for me?
Thank you for your help.
Bernd
Hello,
we use PetaSAN for CIFS and i wonder how to set different settings for some shares.
Example here would be having set "access based share enum = Yes" on some shares but not all.
I understand one could set those settings in CIFS-Settings\Share Secure but this applies to all shares in that case.
Any hints for me?
Thank you for your help.
Bernd
admin
2,930 Posts
March 19, 2022, 12:06 amQuote from admin on March 19, 2022, 12:06 amCurrently, aside from authorization, we support one smb.conf configuration that is applied to all shares. Do you see this as a limitation ?
Currently, aside from authorization, we support one smb.conf configuration that is applied to all shares. Do you see this as a limitation ?
Last edited on March 19, 2022, 12:07 am by admin · #2
BeHau
12 Posts
March 21, 2022, 8:08 amQuote from BeHau on March 21, 2022, 8:08 amYes and no,
of course i could do share-specific changes on smb.conf. This is absolut OK but isn´t that file overwritten when adding another share via GUI? To me it looks like smb.conf is parsed together from "Configuration\CIFS Settings\Advanced" for all shares defined.
I can imagine some ways to solve this. A section in Share Public or Share Secure where one could add extra lines for shares. Those should be respected when parsing smb.conf by clicking the save-button on "CIFS Settings" page.
Could be like "[ShareName]SomeSamabaSetting=Value". Or how about an edit-button next to each share (Manage Cifs\CIFS Shares) do add options to just that share?
Yes and no,
of course i could do share-specific changes on smb.conf. This is absolut OK but isn´t that file overwritten when adding another share via GUI? To me it looks like smb.conf is parsed together from "Configuration\CIFS Settings\Advanced" for all shares defined.
I can imagine some ways to solve this. A section in Share Public or Share Secure where one could add extra lines for shares. Those should be respected when parsing smb.conf by clicking the save-button on "CIFS Settings" page.
Could be like "[ShareName]SomeSamabaSetting=Value". Or how about an edit-button next to each share (Manage Cifs\CIFS Shares) do add options to just that share?
Last edited on March 21, 2022, 8:08 am by BeHau · #3
admin
2,930 Posts
March 21, 2022, 9:40 amQuote from admin on March 21, 2022, 9:40 amYes the file is managed by Consul, it is generated on restarts and settings changes.
We are looking into adding this. But just want to know if this is actually needed, as we always have a goal of not complicating things, but of course without limiting functionality, so any use cases that needs this will help us. We are actually thinking of adding it the same way you describe, if however the user does make share specific configuration then later changes global share settings, do you think we should keep the share specific settings or over-write them ? or ask ?
Yes the file is managed by Consul, it is generated on restarts and settings changes.
We are looking into adding this. But just want to know if this is actually needed, as we always have a goal of not complicating things, but of course without limiting functionality, so any use cases that needs this will help us. We are actually thinking of adding it the same way you describe, if however the user does make share specific configuration then later changes global share settings, do you think we should keep the share specific settings or over-write them ? or ask ?
BeHau
12 Posts
March 21, 2022, 12:57 pmQuote from BeHau on March 21, 2022, 12:57 pmI don't know how many users will use this. However, Petasan supports many use cases. We primarily use it as a file server by now and so the benefit would be very high.
Regarding your question, if there are specific settings for the share and the same parameter is set in Global: Here the specific value should be rated higher and applied.
I don't know how many users will use this. However, Petasan supports many use cases. We primarily use it as a file server by now and so the benefit would be very high.
Regarding your question, if there are specific settings for the share and the same parameter is set in Global: Here the specific value should be rated higher and applied.
Last edited on March 21, 2022, 12:58 pm by BeHau · #5
Where to set share-specific settings?
BeHau
12 Posts
Quote from BeHau on March 18, 2022, 9:40 amHello,
we use PetaSAN for CIFS and i wonder how to set different settings for some shares.
Example here would be having set "access based share enum = Yes" on some shares but not all.
I understand one could set those settings in CIFS-Settings\Share Secure but this applies to all shares in that case.Any hints for me?
Thank you for your help.
Bernd
Hello,
we use PetaSAN for CIFS and i wonder how to set different settings for some shares.
Example here would be having set "access based share enum = Yes" on some shares but not all.
I understand one could set those settings in CIFS-Settings\Share Secure but this applies to all shares in that case.
Any hints for me?
Thank you for your help.
Bernd
admin
2,930 Posts
Quote from admin on March 19, 2022, 12:06 amCurrently, aside from authorization, we support one smb.conf configuration that is applied to all shares. Do you see this as a limitation ?
Currently, aside from authorization, we support one smb.conf configuration that is applied to all shares. Do you see this as a limitation ?
BeHau
12 Posts
Quote from BeHau on March 21, 2022, 8:08 amYes and no,
of course i could do share-specific changes on smb.conf. This is absolut OK but isn´t that file overwritten when adding another share via GUI? To me it looks like smb.conf is parsed together from "Configuration\CIFS Settings\Advanced" for all shares defined.
I can imagine some ways to solve this. A section in Share Public or Share Secure where one could add extra lines for shares. Those should be respected when parsing smb.conf by clicking the save-button on "CIFS Settings" page.
Could be like "[ShareName]SomeSamabaSetting=Value". Or how about an edit-button next to each share (Manage Cifs\CIFS Shares) do add options to just that share?
Yes and no,
of course i could do share-specific changes on smb.conf. This is absolut OK but isn´t that file overwritten when adding another share via GUI? To me it looks like smb.conf is parsed together from "Configuration\CIFS Settings\Advanced" for all shares defined.
I can imagine some ways to solve this. A section in Share Public or Share Secure where one could add extra lines for shares. Those should be respected when parsing smb.conf by clicking the save-button on "CIFS Settings" page.
Could be like "[ShareName]SomeSamabaSetting=Value". Or how about an edit-button next to each share (Manage Cifs\CIFS Shares) do add options to just that share?
admin
2,930 Posts
Quote from admin on March 21, 2022, 9:40 amYes the file is managed by Consul, it is generated on restarts and settings changes.
We are looking into adding this. But just want to know if this is actually needed, as we always have a goal of not complicating things, but of course without limiting functionality, so any use cases that needs this will help us. We are actually thinking of adding it the same way you describe, if however the user does make share specific configuration then later changes global share settings, do you think we should keep the share specific settings or over-write them ? or ask ?
Yes the file is managed by Consul, it is generated on restarts and settings changes.
We are looking into adding this. But just want to know if this is actually needed, as we always have a goal of not complicating things, but of course without limiting functionality, so any use cases that needs this will help us. We are actually thinking of adding it the same way you describe, if however the user does make share specific configuration then later changes global share settings, do you think we should keep the share specific settings or over-write them ? or ask ?
BeHau
12 Posts
Quote from BeHau on March 21, 2022, 12:57 pmI don't know how many users will use this. However, Petasan supports many use cases. We primarily use it as a file server by now and so the benefit would be very high.
Regarding your question, if there are specific settings for the share and the same parameter is set in Global: Here the specific value should be rated higher and applied.
I don't know how many users will use this. However, Petasan supports many use cases. We primarily use it as a file server by now and so the benefit would be very high.
Regarding your question, if there are specific settings for the share and the same parameter is set in Global: Here the specific value should be rated higher and applied.