TrueNAS-24.04.2
It has WORM enabled SMB share.
In “Advanced” section “Additional Parameters String” worm:grace_period = 300
But I can’t change it to another number. It’s not implemented in GUI.
Also I found that /etc/smb4.conf is has only [global] section with a few records.
testparm -s display wide info about server and shares. And it show worm:grace_period = 300 too.
But how can I change worm:grace_period for share permanently?
Hi Zhmak,
i have the very same issue. Were you able to find a solution in the meantime?
On Electriceel, the aux. parameters field has completely disappeared, so I think from a GUI pov there’s no option to do so.
But maybe somehow via cli?
BR
I have created this bug report: Jira
Since they removed Auxiliary Parameters from SCALE, are you suggesting they add multiple WORM presets with different lengths of time?
The GUI for an SMB share could have these different options:
I think that would be a much better implementation in the GUI than to allow users to enter their own Auxiliary Parameters.
Even if such options are hidden behind an “Advanced” toggle with a clear warning of the risks, I don’t think Auxiliary Parameters should ever return.
I think it makes the most sense to constantly keep adding different parameters to the GUI, request after request. 
Oh, lookie lookie here.
@winnielinnie yeah, I saw both those things you linked to before posting here. I’m honestly flabbergasted that they hold this view about disallowing aux params.
ui/system/advanced lets you set sysctls and init/shutdown scripts, why is that ok? 
I’m currently just paying with SCALE, and trying to see which of my aux params have “proper” UI now, and so far it’s only one: being able to require encryption.
Years ago I suggested a “proper” UI for replacing a particular aux param, but no go either: Jira
I could live with no aux params if there were replacements, but so far it seems not to be the case. 
It is honestly the most bizarre thing to happen from Core → SCALE. It’s one of those changes I cannot in good faith pretend to accept, even with the justifications given.
Just don’t expose Auxiliary Parameters to enterprise customers. Mission complete.
For non-enterprise users, they can even just hide them behind an “advanced” toggle, with a clear warning of the risks involved.
To completely gut them seems like a net negative for non-enterprise users. We’re being protected from ourselves?
If that’s the justification, then go ahead and remove the Shell. As you can see, it’s trivial to run rm -rf and destroy your data. Why is that allowed? But we’re not allowed to enter our own WORM grace period? We must accept “no WORM” or “WORM with a preset of 5 minutes”? Nothing else is allowed via the GUI? Why?
Are we really expected to over-clutter the GUI with checkboxes, toggles, radio buttons, and menu selections for every feature that gets “accepted”? This is somehow preferable to a simple Auxiliary Parameters text field?
Needless to say, there are use-cases for custom parameters and options for SSH, SMB service, SMB shares, UPS, NFS, and so on. I think it’s quite silly to solicit “feature requests” for every… single… possible… option that someone might find useful. (Which are usually rejected, anyways.)
It is truly shocking that even after so much backlash from their own power user community, this is still a topic of frustration. A year has past and still they continue to close Jira feature suggestions or bug submissions for something as simple as SMB share parameters. For those that stumble on this, this solution still works (verified on scale dragonfish): https://www.truenas.com/community/threads/auxiliary-parameters-missed.113938/page-3
Jira feature suggestions moved to Feature Requests - TrueNAS Community Forums
This is the method they are now using.
You could try this:
cli then sharing smb query. Take a note of the share IDsharing smb update id=7 auxsmbconf=“worm:grace_period = 100”testparm -s to confirm your changes have taken effectReplace the ID I used with your share ID and the grace period to something more appropriate to you.
This method requires you to remember to do this every time you change the share settings.
But it works! Thanks!
It looks like WORM_DROPBOX “purpose” defines smb share parameters such a “auxsmbconf”
I think the best way would be to change the “purpose” preset WORM_DROPBOX. I wish I knew where to edit it
Yes, thank you, this is the method described in the link I pasted above.
Do you change your share settings often? I generally don’t.
I think the presets are helpful and best left unchanged. However I agree it would be nice to have somewhere in the UI to make these changes.
Yes indeed, sorry I didn’t follow that link till after I posted but the gist is the same.
There is a simple and safe solution, which will not risk the quality or stability of enterprise products: Make it only available for the “Community” edition, and hide such text fields by default.
I don’t understand the resistance to this approach.
TrueNAS Enterprise: no auxiliary parameters, not even behind a “hidden” option
TrueNAS Community: no accessible auxiliary parameters, unless the user explicitly unhides them, after being met with a warning disclaimer
How is this bad?
I would argue that removing Auxiliary Parameters introduces more problems, since users who insist on using them anyways are partially “blind”, forced to throw terminal commands at shares and services, without a UI to review and verify.
My guess is that the main concern is users making changes and getting odd behaviour regardless of if they are an Enterprise customer or not. Enterprise customers I dare say are much less likely to play around with these settings as bad things can happen and instead consult with iX if a certain setting is required.
The options are either A. Lock it down to only approved and tested configurations or B. Open it up to the Wild West (like before).
I do get where they are coming from but equally I tend to agree with you.
Not this.
Rather, this:
A. Lock it down to only approved and tested configurations, for Enterprise
B. Lock it down to only approved and tested configurations (but with the option to unhide Auxiliary Parameters with a clear warning), for Community
Hilariously, you can install TrueNAS “Community” Edition on a laptop with a cheap Realtek dongle, and with an external drive attached to a USB port as a non-redundant single-drive pool, with only 8 GiB of RAM.
But heaven forbid you “risk” anything with Auxiliary Parameters…