I do see uses, eg: Migration, Transfer, Tests (!)…
These are not “normal” conditions, but are use cases during hardware upgrades, migration of Users, etc… This is useful even on small and medium sized networks…
Think of NethServers backup mount when using duplicity - it’s only mounted during backups, then unmounted…
This week, I need to migrate a total of 4 Mac Minis at a doctors practice… 2 brand new Mac Minis with M1 chip, and 2 two year old Mac Minis, 2 6 year old Mac Minis will be replaced.
As Apple’s M1 chip can’t yet run parallels or virtualbox with Windows (Needed for the doctors software and the dictation stuff…), we need to shuffle the stuff around.
In short, the doctor bought the 2 M1 too soon, before asking me… Sh*t happens…
My 2 cents
Andy
The doctor’s software runs on Windows, but the X-Ray / DICOM stuff runs on Mac, this way, we get the best of both on one screen…
I can run the doctors software with RDP, but NOT the dictation software…
preparation of the share before publishing with all data available and permissions ready when the share should be accessible
temporary deny access to a share preserving the authorizations (investigations?)
a way for define and preserve data received during a migration until a deadline
Which could not been understood as enough from advisors and it won’t preserve already setup ACLs (which may be subject to thirdy party evaluation and or approval)
It seems the use case is very limited, so why not just temporary renaming the dir?
Example: you have a ibay named test, if you want to temporary disable it just: mv /var/lib/nethserver/ibay/test /var/lib/nethserver/ibay/test.inaccessible. ACL will be preserved.
a) skip the shared folder in smb.conf template expansion (samba share is not defined at all)
b) define the share in smb.conf but make it not accessible: it is there, but nobody can access it