How to run pkg upgrade from Diagnostics → Command Prompt
-
I come back to your answer and my answer where I said that this command worked (which is still the case).
But why doesn't this menu appear by itself? I set the original "user" "admin" to disabled and created another "admin" with another name, is that why the menu doesn't appear by itself?
I've also installed the "sudo" package, if this information helps to solve my problem.
-
@SwissSteph said in How to run pkg upgrade from Diagnostics → Command Prompt:
But why doesn't this menu appear by itself? I set the original "user" "admin" to disabled and created another "admin" with another name, is that why the menu doesn't appear by itself?
=>
@stephenw10 said in How to run pkg upgrade from Diagnostics → Command Prompt:
You can run
/etc/rc.initialto bring up the menu. Though some options there require the admin/root user.See also : Admin Access.
-
The admin user is set to use the console menu as it's shell directly. For other users you need to add it to the tcsh config. Which can now easily be done because of: https://redmine.pfsense.org/issues/14746
For example when logged in as that user run:echo /etc/rc.initial >> ~/.tcshrc.local
Then logout and back in.Steve
-
-
No longer works in 24.03_1, this command "echo /etc/rc.initial >> ~/.tcshrc.local" had worked perfectly on 23.09.1
Should I run another command?
and every time I connect to SSH I get this message:
-
You mean in order to show the console menu for a non-admin user?
-
Yes ... let's say I'm also an adminnistrator
I only have one user (me) and I'm the administrator. Your command worked perfectly the other day and now I don't have the menu and the command doesn't work anymore
-
Ah that's interesting. I assume you have changed the admin password from the default?
And you see that after having run that command?
-
My "user" and "password" are the same as the original ones, with the addition of "before" and "after" letters and numbers.
EDIT
I confirm, I created another user with no letters like the original user and the original password and I no longer have the message shown here.
My problem is therefore with the name of my "administrator" user and its "password".
I'll have to change all that, sorry for my messages ...
-
@Gertjan said in How to run pkg upgrade from Diagnostics → Command Prompt:
Putty.
It's a the best SSH client (IMHO of course). Some extra tools come with it.Maybe if you don't have access to securecrt, which is not free. Use to be a big putty guy, and it is pretty solid.. But when your on shell to remote devices all day.. securecrt is really nice.
I haven't played with windows "native if you will" ssh client - it was always behind from when first started playing with it. I do like options, so I always install the openssh client from here.
https://www.mls-software.com/opensshd.html
They are normally pretty current on the version.
C:\>SSH -V OpenSSH_9.7p1, OpenSSL 3.0.13 30 Jan 2024 -
Yeah it's an edge case triggering the enforced password change. I see that here. Digging....
-
I've created a user and password that have nothing to do with the original ones -> OK, I can connect via SSH without any problems or error messages.
Once connected, if I run the command "echo /etc/rc.initial >> ~/.tcshrc.local" -> OK
I reconnect and get this error message again:
I think I may have found a "bug" !?
-
Yes, I replicated it. We are looking into it now....
-
@stephenw10
Thank you for your confirmation -
Ok fix from @jimp incoming. Working for me here. Should be up shortly....
-
S SwissSteph referenced this topic on
