Posts by Bo Beagle
-
-
This should work
Thanks for the tip, I will try it.
Seems a bit strange that you can’t set a time when Time of execution is set to Daily.
Can you confirm that a Daily task is executed at midnight?
-
What is the Standby mode setting in System>Power Management>Settings?
What does it mean when it set to Power Off?
-
At what time will a daily shutdown start?
In System>Power Management>Scheduled Tasks. I have the following task: Shutdown Daily (see attachment).
It seems to be at midnight 00:00h, but why?
I did expect it to be at 6:25h AM
> grep run-parts /etc/crontab
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron
( cd / && run-parts --report /etc/cron.daily )47 6 * * 7 root test -x /usr/sbin/anacron
( cd / && run-parts --report /etc/cron.weekly )52 6 1 * * root test -x /usr/sbin/anacron
( cd / && run-parts --report /etc/cron.monthly )What if I want it to be at 00:30h AM?
-
I want to have a home directory for every user I create in openmediavault.
And I want this home directory to be the ordinary linux home directory (i.e. “/home/<username>”)
Is my solution correct???- I installed the sharerootfs plugin to enable Shared Folders on the root partition.
- I created a Shared Folder named Home on the root partition (/dev/sda2) with relative directory home/
Remark: /home in my case is a mounted partition (/dev/sda4) can this be a problem?
- I enabled User home directory in Users > Settings using the created Home shared folder as location.
/etc/fstab:
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=0abfcc38-444a-4b4e-8350-d40a46ccb377 / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=37a14b16-0b13-4313-b24f-c920de1cc82d /boot ext2 defaults 0 2
/dev/sda4 /home ext4 defaults 0 2
# swap was on /dev/sda3 during installation
UUID=b92ed486-2aef-4577-b740-cc9e7ecadcff none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/c6cad986-b2de-4106-a9ac-cad2103d0810 /srv/dev-disk-by-uuid-c6cad986-b2de-4106-a9ac-cad2103d0810 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]
-
Did you have a chance to read through documentation? It still may be confusing after the first read, but it is rather comprehensive:
No, thank you! I will have a look
-
-
-
While there might be a couple issues with the plugin due to lack of testers, the webdav part is served by nginx which should be very stable. Are you running on mission critical system?
Noops
-
Is it stable?
When I select Testing repo in System > omv-extras > Settings and press the Save button:
It says "Please wait..." for a while followed by "Error 504 Gateway time-out"
After refreshing the webpage it seems ok
-
The openmediavault-webdav plugin?
Where can I find that plug-in, I don’t see it.
Is it in testing?
-
-
omv-salt deploy run fstab
What about the following modules that are also dirty:
- collectd
- monit
- quota
-
omv-rpc -u admin 'filesystemmgmt' 'setMountPoint' '{ "id": "/dev/sdb1", "usagewarnthreshold": 85, "comment": "" }' ??
Which omv-salt command should follow?
Is there a general (omv-salt) command that i can issue for no matter what pending configuration changes that handles all dirty modules?
-
Executing the command: sudo omv-confdbadm create conf.system.filesystem.mountpoint
Gives the following error: ERROR: Failed to create the default configuration: [Errno 13] Permission denied: '/usr/share/openmediavault/confdb/create.d/'
-
Read his sentence again. He says without OMV.
I told you already. Edit the xml (xmlstarlet works well from scripts) and then run omv-salt deploy run ssh.
I know he said "without OMV", but I don't know what he means, hence my apparently silly question to trigger a more elaborate explanation.
OK, I will directly edit the config.xml file.
Thanks for the xmlstarlet tip!
-
In that case i suggest to use plain Salt or Ansible without OMV as a (blocking/unflexible) layer between your system and your w
Shouldn't I use that when I want to change Linux config files that are already "controlled" and overwritten by OMV?
-
OMV acts like it does because it was never the intention to give power users the ability to do weird things. It's working that way that it solves its job, getting the configuration parameters from the UI or any RPC and stores them in the database. Salt is then deploying the configuration and services. OMV acts as root of origin in the system. That's the main intention of OMV. And it will stay that way.
I fully understand! As a rookie I wouldn't even dare to ask you to change a thing in OMV.
I only want to change a few settings via a shell script (cli). The reason I don't want to do that in the WebUI is convenience and to make sure I don't forget to change a setting in the WebUI after installing OMV.
I only want to know the best way to achieve this.
-
The following seems to work but is ugly:
omv-rpc -u admin 'SSH' 'set' `omv-rpc 'SSH' 'get' | jq -c '.permitrootlogin = false'`
What about using omv-confdbadm?
-
This doesn't work:
sudo omv-rpc -u admin 'SSH' 'set' '{"permitrootlogin": false}' | jq
It seems I need to specify all attributes of the object.
{
"enable": true,
"port": 22,
"passwordauthentication": true,
"pubkeyauthentication": true,
"permitrootlogin": false,
"tcpforwarding": false,
"compression": false,
"extraoptions": ""
}
What if I only want tot change one attribute (i.e. permitrootlogin)?
