Posts by votdev

    Is this an answer to your question?

    Partly. I wanted to know which language you've selected during the installation, e.g. geman, english, french, ...

    fabiopaolini How is this possible? OMV5 is based on Debian Buster which uses ProFTPd 1.3.6. In this version the mod_ident is compiled by default and not as an external module that needs to be enabled. Are you using a backport from Debian Bullseye? Using backports is not supported in OMV because of exactly the problem you are facing now, backports break existing configurations and introduce new features that are not reflected by the deployment scripts.

    The plugin is just trying to find the hostname to open a browser window. I used to use the javascript function location.hostname to build the url but I can't do that anymore. I don't care if the hostname has been modified but not applied because the plugin needs the current name that is resolving. Salt can't be used here either because this is all client side stuff.

    OK, that is an easy task. Simply use {{ location.hostname }} in a string, and the UI will automatically fill it with the current hostname. See…/functions.helper.ts#L307

    The code is using php's function gethostname since I can't use javascript to get the hostname anymore. I may have to execute the command hostname -f and use its output. Does hostname -f return the correct hostname on your system?

    Unfortunately, it isn't cut&paste.

    The symlinks plugin shouldn't be a problem to port since it is pretty simple.

    ryecoaaron You can use \OMV\System\Net\DNS to get the hostname, but the better approach is to load the database object and build the hostname yourself. Think about the situation where the hostname is modified but not applied, then your plugin is modified and the PHP code uses gethostname to get the hostname, this will finally end in incorrect data.

    I don't know the plugin, but why not getting the hostname while deploying the configuration. You can use Salt grains to get the hostname or easily access the database object. You can make 'hostname' a dependency of your RPC module, thus 'hostname' is deployed before your plugin, and you can be sure the Salt grain contains the correct hostname.

    8. I dug in to understand what it will take to do that and if it will break everything, and found this:…port.cgi?att=1;bug=982530 - it seemed pretty serious and potentially installation-breaking, so I did not touch any of the files in /etc/pam.d/ (grep-ing showed 4 configs containing the modules)

    You are surely using backports (libpam-modules 1.4.0-7 was introduced in Debian 11 and is maybe available via the backports repo) which is strictly forbidden in OMV because of exactly this problem you are now running into. Backports may break existing implementations/workflows through incompatibilities, because of that OMV is only based on the stable branch.

    To install OMV6 on an already installed Debian 11 (Bullseye), simply execute the following steps: