Update openmediavault available

The following changes has been done:

  • Fix bug in regex to parse date/time field in RSync logfile
  • Modify various default settings for SMB/CIFS, FTP and TFTP
  • Mantis 0000312: Shared Folders – Show Label not only Volume
  • Mantis 0000314: Can’t add shared folder with same name on another volume

Please update your system via ‘System > Update Manager’ in the OpenMediaVault WebGUI. Please reload the WebGUI to let the changes installed by the update take effect.

New updates available


  • Fix bug in omv-firstaid when configuring the network interface.
  • Add environment variable OMV_HTTPREQUEST_TIMEOUT to modify the WebGUI HTTP request timeout. Defaults to 60000 milliseconds.
  • Improve monitoring implementation (via monit)
  • Mantis 0000104: General Settings: Error while changing session timeout
  • Mantis 0000294: creating two smb shares with the same name on two shared folders
  • Mantis 0000300: Change bond mode fails and requires reboot
  • Mantis 0000303: Samba log settings prevent non-error logging
  • Mantis 0000306: Diagnostics – System logs do not display correct order of column ‘Date & Time’

openmediavault-forkeddaapd 0.2.2

  • Improve monitoring implementation (via monit)

Please update your system via ‘System > Update Manager’ in the OpenMediaVault WebGUI.

Please update all packages at the same time, otherwise you may run into dependency problems.

Current project state

No new updates does not mean development has been stopped. Since the release of OMV various issues came up which have to be improved in the next time. One of the important ones are:

  • Improve user homes implementation.
  • Modify/simplify shared folder permission handling.
  • Split WebGUI and RPC processing into different parts. A daemon process will handle the RPC request and communicates via socket with the WebGUI.
  • Use an embedded XML database instead of a plain XML file for configuration. Currently Sedna or Oracle DBXML are my favorites. Why using a XML database and not SQLite or something else? Because OMV is already using a XML file for its configuration and the complete backend is using XPath/XQuery when generating the configuration files. Using a XML database will not need to change the backend, too. Why using an embedded database? Because the current plain file does not support transaction handling (most important problem right at the moment) and all the features a database has. When starting OMV long time ago i did not think about that this will become a problem (due FreeNAS has no probs with a plain file for years), but things change.

New updates available


  • Make sure a rsync cron job is not executed while it is still running.
  • Mantis 0000272: Allow handleResponse in OMVDownloadRpcServer to accept a content type
  • Mantis 0000287: After upgrade to, system graph are not refreshed anymore


  • To much to list all those new features here. Thanks to Marcel Beck to contribute this.

Please update your system via ‘System > Update Manager’ in the OpenMediaVault WebGUI.

Note, if you update from openmediavault < please deinstall the netatalk and forkeddaapd plugins via WebGUI before upgrading core package to the latest version to prevent installation errors.