Closed adriaandegroot closed 6 years ago
.. one (only?) case where this happens is in shared/vzvol_permissions.sh
where there's a zfs set custom:fs=none .. command not guarded by a check for ZROOT != root. That's why using a shell-function for su might be better, you can lose the guards elsewhere in the scripts and systematically use $VZVOL_SU_CMD everywhere.
CLosing as this functionality will be removed shortly to rely only on sudo, and will check if already running as root
When running vzvol as root, the su command should probably be left blank / do nothing, since there's no need to su. Something like this, perhaps: