You should not use the linking feature, as it seams to be broken. Clicking on post #14 links to post #9, but the quote shown in that post is from post #1. So it was not clear what you wanted to ask. But if you think insulting the people who try to help is the way to go .....Did you even read my post $9 which I even linked here again in post #14?
Ouch! As I mentioned, you should read some basics on shell commands and how Unix rights/permissions work, as you don't seem to understand whatI enabled the root login in SSH settings, then logged in as root and typed su.
su
does or what the root account is.They where clear, but it looks like you did not get it right. You asked:The instructions were pretty clear. Log in as root and type su.
And this is the correct answer:I am trying to get non-root account to be able to use the smartctl command.
Type SU once you are logged in with putty and enter the root password.
Hi Octopuss, The reason you have the "su: Sorry" is because you must have your root account "Enable password login" set to "No".And the answer didn't work, because when I do so, this happens:
octopuss@Skladiste:~ % su
su: Sorry
I already pointed that out three times (minus the shell output) and nobody seemed to notice.
No, the opposite. The root account must be set to allow root login in order for the "su" command to be successful and not return the "su:Sorry" message.So su requires disabling the ability to log in to the entire system with the root account? Ok...
Nothing about Linux makes any sense :D
It will work if your user is part of the Wheel group.No, the opposite. The root account must be set to allow root login in order for the "su" command to be successful and not return the "su:Sorry" message.
Working fine for me.Hi Octopuss, The reason you have the "su: Sorry" is because you must have your root account "Enable password login" set to "No".
login as: Jailer Jailer@192.168.0.200's password: Last login: Sat Nov 2 09:12:35 2019 from 192.168.0.210 FreeBSD 11.2-STABLE (FreeNAS.amd64) #0 r325575+fc3d65faae6(freenas/11.2-stable): Wed Dec 5 15:08:42 EST 2018 FreeNAS (c) 2009-2017, The FreeNAS Development Team All rights reserved. FreeNAS is released under the modified BSD license. For more information, documentation, help or support, go here: http://freenas.org Welcome to FreeNAS Jailer@freenas:~ % su Password: root@freenas:/nonexistent #
login as: root root@192.168.0.200's password: Last login: Fri Nov 1 13:14:36 2019 from 192.168.0.210 FreeBSD 11.2-STABLE (FreeNAS.amd64) #0 r325575+fc3d65faae6(freenas/11.2-stable): Wed Dec 5 15:08:42 EST 2018 FreeNAS (c) 2009-2017, The FreeNAS Development Team All rights reserved. FreeNAS is released under the modified BSD license. For more information, documentation, help or support, go here: http://freenas.org Welcome to FreeNAS Warning: settings changed through the CLI are not written to the configuration database and will be reset on reboot. root@freenas:~ #
No I use password authentication.Do you have you root account set as the screenshot?
This would be the expected behavior. Doing aWell, for me my account as a user is set to Wheel under Auxiliary Groups, and yet I can't do "su" successfully if "Root" is not allowed.
su -
as user basically is a password login as root.This is probably not what you meant, right? You wanted the OP to check if his setting is "No" while it should be "Yes"?The reason you have the "su: Sorry" is because you must have your root account "Enable password login" set to "No".
That's why I expected smartctl to work in the first place - got that checked since the beginning.BTW, one can also give a user root permissions checking the "[ ] permit sudo" checkbox in the user settings.
And yet, you never posted exactly what you did. The first time in post #25 you actually posted a command you issued and the resulting error message.That's why I expected smartctl to work in the first place - got that checked since the beginning.
My normal user account has the "[ ] permit sudo" checkbox checked, and the root account is not allowed to use password to login.This would be the expected behavior. Doing asu -
as user basically is a password login as root.
I think the confusion comes from this statement:
This is probably not what you meant, right? You wanted the OP to check if his setting is "No" while it should be "Yes"?
BTW, one can also give a user root permissions checking the "[ ] permit sudo" checkbox in the user settings.