You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
logname tells you the user who originally opened the terminal, not the actual current user.
For example, the following user is a user named "fred" I "su'd" to under "sean". I also specified the user with the -u flag. But it still creates a vmdk in /home/sean.
fred@debian:~$ sudo vzvol -s 10m -t virtualbox -v virttest5 -u fred
creating a vzol of size
10m
Testing to ensure zvol was created
/dev/zd928
DIE
Creating /home/sean/VBoxdisks/virttest5.vmdk
RAW host disk access VMDK file /home/sean/VBoxdisks/virttest5.vmdk created successfully.
Please use /home/sean/VBoxdisks/virttest5.vmdk as your VM Disk
fred@debian:~$ logname
sean
The text was updated successfully, but these errors were encountered:
Under X11 (Plasma started from SDDM) on 11.2-STABLE, logname prints root when run from xterm or konsole. ssh'ing to localhost gets me the expected (not-root) username. So my vmdk's get created in /root instead of my own home dir. (Maybe running vzvol from a graphical environment on FreeBSD isn't one of your common use-cases, though)
@adriaandegroot Definitely not a common use-case.
Under 11.2-RELEASE, in an LXDE environment, however, this issue isn't present. This leads me to believe that KDE is fucking something up.
logname tells you the user who originally opened the terminal, not the actual current user.
For example, the following user is a user named "fred" I "su'd" to under "sean". I also specified the user with the -u flag. But it still creates a vmdk in /home/sean.
The text was updated successfully, but these errors were encountered: