Hello!
Curious...
I have been manually updating the file `/etc/avahi/services/smb.service` to remove the extra bits that the system adds to the share name. But, no matter the changes I am applying, the file is overwritten, and I have to log back in and change it again. I have event chattr +i the file, which resulted in 500 error when applying changes. Why can't this be a configuration change with the GUI? Was it ever? Anyway, any help would be appreciated. 
Curious...
I have been manually updating the file `/etc/avahi/services/smb.service` to remove the extra bits that the system adds to the share name. But, no matter the changes I am applying, the file is overwritten, and I have to log back in and change it again. I have event chattr +i the file, which resulted in 500 error when applying changes. Why can't this be a configuration change with the GUI? Was it ever? Anyway, any help would be appreciated.
This is no mystery, it's how OMV works. In general you should not manually edit the files, only edit the GUI settings. OMV is responsible for reconfiguring those files every time you modify something in the GUI.
In the case of Samba you can use the additional options field to add custom commands.
You should use the OMV_SAMBA_ZEROCONF_NAME environment variable (which defaults to%h - SMB/CIFS) to customize the name that is announced by Avahi.
You should use the OMV_SAMBA_ZEROCONF_NAME environment variable (which defaults to%h - SMB/CIFS) to customize the name that is announced by Avahi.
votdev thank you, this resolved the issue for me.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
