Posts by guy2545

Dabbling back with OMV after a long absence.

It seems every time I restart samba (via the web interface after adding a share), it joins my AD Windows Server 2022 via winbind even though it was already domain joined from sssd.

So now I have the same AD domain listed twice, once via winbind and once via sssd. This appears to be causing login issues for any of the Samba shares.

Maybe I am misunderstanding something, but why is OMV joining the domain again via winbind, when it is already connected via sssd? Trying to figure out what is triggering the winbind join.

It would be a lot of work to bring it up, and if only for a few months before 0.5 it would hardly be worth it. I saw the 0.5 API, which is what prompted the question regarding 0.4 API. I will be taking a closer look this weekend to try and figure out what we can expect from 0.5. Great product regardless.

So I am attempting to update the greyhole plugin. I have a lot of experience with greyhole setup and configuration through the command line. I have been able to successfully install the old greyhole plugin for the 0.3 version of OMV, however it took a lot of command line massaging for it to work. The binary package of the plugin fails to do a lot of things that greyhole requires to work such as setting up the mysql database properly, or even install greyhole itself.

The biggest problem I am running into now is working through some of the API calls of the GUI portion of the plugin. I have never been much of a GUI programmer, so anything I really attempt is a hack. The first thing I noticed was when you try to remove a samba share through the greyhole plugin, it would ask you "are you sure you want to do this?" But it does not present the user with a yes, no or cancel.

If the developers approve, I will post a walk through of all the steps I went through to get it to work. Of course, this is strictly for ALPHA testing only and I have only done it with a fresh install on a virtual machine. I have not attempt to copy over any previous greyhole configs and had no concern with any pre-existing data within the greyhole "array".

Basically, do no attempt this if you value your data.

Quote from "drap"

Having said all of the above, I have noticed a slight problem. I believe during updates the /etc/samba/smb.conf file gets over written and manual changes I made for Greyhole settings get lost. For example, the smb.conf file should have lines such as

Code

[global]
unix extensions = no
wide links = yes
[Videos]
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole

However I those chances have been lost, I assume this happened during some update.
Can anyone help as to how to makes these changes persistent through updates?
Thank you.

I have noticed the same problem (also run greyhole from the cli). I added a couple lines to the monitrc to try and detect if the file was changed. If it is changed, then monit will stop samba, copy over the backup smb.conf and then restart samba, then restart greyhole and restart mount_shares_locally.