Why aren't my ~/.login_conf settings respected when ssh into FreeBSD?adjust zfs settings on freebsd 9When you...
Would there be balance issues if I allowed opportunity attacks against any creature, not just hostile ones?
In chocolate terminology, what is the name of thinly sliced leaf-shaped toppings made from hot, smooth chocolate, used to form flower petals?
Why did the VIC-II and SID use 6 µm technology in the era of 3 µm and 1.5 µm?
Function of the separated, individual solar cells on Telstar 1 and 2? Why were they "special"?
Sum of Infinite series with a Geometric series in multiply
Were the women of Travancore, India, taxed for covering their breasts by breast size?
Can my UK debt be collected because I have to return to US?
'Hard work never hurt anyone' Why not 'hurts'?
Displaying minutes in HH:MM format
Why don't they build airplanes from 3D printer plastic?
Map a function that takes arguments in different levels of a list
In Toy Story, are toys the only inanimate objects that become alive? And if so, why?
A question about dihedral group
Can there be plants on the dark side of a tidally locked world?
How to align values in table according to the pm and point?
Do index funds really have double-digit percents annual return rates?
Given a specific computer system, is it possible to estimate the actual precise run time of a piece of Assembly code
Meaning of "offen balkon machen"?
I have two helper functions that are the exact same, one executes and one doesn't. How come?
Does the Scrying spell require you to have a clear path to the target in order to work?
How to add some symbol (or just add newline) if the numbers in the text are not continuous
Punishment in pacifist society
Visiting girlfriend in the USA
Why does this syntax outputs an error under METAFUN/METAPOST?
Why aren't my ~/.login_conf settings respected when ssh into FreeBSD?
adjust zfs settings on freebsd 9When you ssh into a server, do you use server settings or your own settings?Jenkins does not use system's localesLMDE2 / MATE locale charset inconsistencyunixODBC 2.3.0 “_S_create_c_locale name not valid” errorAccess denied SSH from windows to linux via puttyHow do I add a language in FreeBSD?FreeBSD sudo root and ssh-agent
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I connect to a local FreeBSD server (which I administer) via ssh from my laptop. I have a stock FreeBSD 11.2 /etc/login.conf file. I have appended the following to my ~/.login_conf file:
:me
:charset=UTF-8:
:lang=en_CA.UTF-8:
Reading the FreeBSD handbook, 22.2. Using Localization, I would expect that my LANG and other locale variables would be set for me when I connect via ssh.
When I connect, I expect to see:
% locale
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_ALL=
Instead, I see this:
% locale
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
It looks to me as if my ~/.login_conf file is not being respected.
Why is my ~/.login_conf file is not being respected? How can I make it have effect?
Some further information: yes, i have run cap_mkdb after changing my login configuration. This is how they look:
% ls -lF /etc/login* ~/.login*
-rw-r--r-- 1 root wheel 1853 Jun 21 2018 /etc/login.access
-rw-r--r-- 1 root wheel 6790 Jun 21 2018 /etc/login.conf
-rw-r--r-- 1 root wheel 16384 Sep 2 16:41 /etc/login.conf.db
-rw-r--r-- 1 meee meee 392 Aug 22 01:04 /home/meee/.login
-rw-r--r-- 1 meee meee 214 Sep 2 16:23 /home/meee/.login_conf
-rw-r--r-- 1 meee meee 16384 Sep 2 16:23 /home/meee/.login_conf.db
-rw-r--r-- 1 meee meee 214 Sep 2 16:11 /home/meee/.login_conf~
I understand I need to start a new session to have the new locale settings take effect. I understand that exiting an ssh session on the FreeBSD server, then re-connecting to FreeBSD via ssh, starts a new login session. So I expect this is enough to let the ~/.login_conf take effect. But it doesn't seem to work.
The following command makes locale return the correct result for the rest of the current session:
% LANG=en_CA.UTF-8; export LANG ; MM_CHARSET=UTF-8; export MM_CHARSET
It is a workaround, but I would prefer for ~/.login_conf to work reliably.
ssh freebsd login locale
add a comment |
I connect to a local FreeBSD server (which I administer) via ssh from my laptop. I have a stock FreeBSD 11.2 /etc/login.conf file. I have appended the following to my ~/.login_conf file:
:me
:charset=UTF-8:
:lang=en_CA.UTF-8:
Reading the FreeBSD handbook, 22.2. Using Localization, I would expect that my LANG and other locale variables would be set for me when I connect via ssh.
When I connect, I expect to see:
% locale
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_ALL=
Instead, I see this:
% locale
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
It looks to me as if my ~/.login_conf file is not being respected.
Why is my ~/.login_conf file is not being respected? How can I make it have effect?
Some further information: yes, i have run cap_mkdb after changing my login configuration. This is how they look:
% ls -lF /etc/login* ~/.login*
-rw-r--r-- 1 root wheel 1853 Jun 21 2018 /etc/login.access
-rw-r--r-- 1 root wheel 6790 Jun 21 2018 /etc/login.conf
-rw-r--r-- 1 root wheel 16384 Sep 2 16:41 /etc/login.conf.db
-rw-r--r-- 1 meee meee 392 Aug 22 01:04 /home/meee/.login
-rw-r--r-- 1 meee meee 214 Sep 2 16:23 /home/meee/.login_conf
-rw-r--r-- 1 meee meee 16384 Sep 2 16:23 /home/meee/.login_conf.db
-rw-r--r-- 1 meee meee 214 Sep 2 16:11 /home/meee/.login_conf~
I understand I need to start a new session to have the new locale settings take effect. I understand that exiting an ssh session on the FreeBSD server, then re-connecting to FreeBSD via ssh, starts a new login session. So I expect this is enough to let the ~/.login_conf take effect. But it doesn't seem to work.
The following command makes locale return the correct result for the rest of the current session:
% LANG=en_CA.UTF-8; export LANG ; MM_CHARSET=UTF-8; export MM_CHARSET
It is a workaround, but I would prefer for ~/.login_conf to work reliably.
ssh freebsd login locale
add a comment |
I connect to a local FreeBSD server (which I administer) via ssh from my laptop. I have a stock FreeBSD 11.2 /etc/login.conf file. I have appended the following to my ~/.login_conf file:
:me
:charset=UTF-8:
:lang=en_CA.UTF-8:
Reading the FreeBSD handbook, 22.2. Using Localization, I would expect that my LANG and other locale variables would be set for me when I connect via ssh.
When I connect, I expect to see:
% locale
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_ALL=
Instead, I see this:
% locale
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
It looks to me as if my ~/.login_conf file is not being respected.
Why is my ~/.login_conf file is not being respected? How can I make it have effect?
Some further information: yes, i have run cap_mkdb after changing my login configuration. This is how they look:
% ls -lF /etc/login* ~/.login*
-rw-r--r-- 1 root wheel 1853 Jun 21 2018 /etc/login.access
-rw-r--r-- 1 root wheel 6790 Jun 21 2018 /etc/login.conf
-rw-r--r-- 1 root wheel 16384 Sep 2 16:41 /etc/login.conf.db
-rw-r--r-- 1 meee meee 392 Aug 22 01:04 /home/meee/.login
-rw-r--r-- 1 meee meee 214 Sep 2 16:23 /home/meee/.login_conf
-rw-r--r-- 1 meee meee 16384 Sep 2 16:23 /home/meee/.login_conf.db
-rw-r--r-- 1 meee meee 214 Sep 2 16:11 /home/meee/.login_conf~
I understand I need to start a new session to have the new locale settings take effect. I understand that exiting an ssh session on the FreeBSD server, then re-connecting to FreeBSD via ssh, starts a new login session. So I expect this is enough to let the ~/.login_conf take effect. But it doesn't seem to work.
The following command makes locale return the correct result for the rest of the current session:
% LANG=en_CA.UTF-8; export LANG ; MM_CHARSET=UTF-8; export MM_CHARSET
It is a workaround, but I would prefer for ~/.login_conf to work reliably.
ssh freebsd login locale
I connect to a local FreeBSD server (which I administer) via ssh from my laptop. I have a stock FreeBSD 11.2 /etc/login.conf file. I have appended the following to my ~/.login_conf file:
:me
:charset=UTF-8:
:lang=en_CA.UTF-8:
Reading the FreeBSD handbook, 22.2. Using Localization, I would expect that my LANG and other locale variables would be set for me when I connect via ssh.
When I connect, I expect to see:
% locale
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_NUMERIC="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_ALL=
Instead, I see this:
% locale
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
It looks to me as if my ~/.login_conf file is not being respected.
Why is my ~/.login_conf file is not being respected? How can I make it have effect?
Some further information: yes, i have run cap_mkdb after changing my login configuration. This is how they look:
% ls -lF /etc/login* ~/.login*
-rw-r--r-- 1 root wheel 1853 Jun 21 2018 /etc/login.access
-rw-r--r-- 1 root wheel 6790 Jun 21 2018 /etc/login.conf
-rw-r--r-- 1 root wheel 16384 Sep 2 16:41 /etc/login.conf.db
-rw-r--r-- 1 meee meee 392 Aug 22 01:04 /home/meee/.login
-rw-r--r-- 1 meee meee 214 Sep 2 16:23 /home/meee/.login_conf
-rw-r--r-- 1 meee meee 16384 Sep 2 16:23 /home/meee/.login_conf.db
-rw-r--r-- 1 meee meee 214 Sep 2 16:11 /home/meee/.login_conf~
I understand I need to start a new session to have the new locale settings take effect. I understand that exiting an ssh session on the FreeBSD server, then re-connecting to FreeBSD via ssh, starts a new login session. So I expect this is enough to let the ~/.login_conf take effect. But it doesn't seem to work.
The following command makes locale return the correct result for the rest of the current session:
% LANG=en_CA.UTF-8; export LANG ; MM_CHARSET=UTF-8; export MM_CHARSET
It is a workaround, but I would prefer for ~/.login_conf to work reliably.
ssh freebsd login locale
ssh freebsd login locale
asked 1 hour ago
Jim DeLaHuntJim DeLaHunt
1155 bronze badges
1155 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You maybe need to run cap_mkdb; see
https://forums.freebsd.org/threads/login_conf-ignored-at-login.31782/
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already rancap_mkdbon both/etc/login.confand~/.login_conf. I included that in my "further information". Any other ideas?
– Jim DeLaHunt
46 mins ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f538776%2fwhy-arent-my-login-conf-settings-respected-when-ssh-into-freebsd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You maybe need to run cap_mkdb; see
https://forums.freebsd.org/threads/login_conf-ignored-at-login.31782/
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already rancap_mkdbon both/etc/login.confand~/.login_conf. I included that in my "further information". Any other ideas?
– Jim DeLaHunt
46 mins ago
add a comment |
You maybe need to run cap_mkdb; see
https://forums.freebsd.org/threads/login_conf-ignored-at-login.31782/
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already rancap_mkdbon both/etc/login.confand~/.login_conf. I included that in my "further information". Any other ideas?
– Jim DeLaHunt
46 mins ago
add a comment |
You maybe need to run cap_mkdb; see
https://forums.freebsd.org/threads/login_conf-ignored-at-login.31782/
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You maybe need to run cap_mkdb; see
https://forums.freebsd.org/threads/login_conf-ignored-at-login.31782/
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
Kaitlin Duck SherwoodKaitlin Duck Sherwood
101
101
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Kaitlin Duck Sherwood is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already rancap_mkdbon both/etc/login.confand~/.login_conf. I included that in my "further information". Any other ideas?
– Jim DeLaHunt
46 mins ago
add a comment |
1
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already rancap_mkdbon both/etc/login.confand~/.login_conf. I included that in my "further information". Any other ideas?
– Jim DeLaHunt
46 mins ago
1
1
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already ran
cap_mkdb on both /etc/login.conf and ~/.login_conf. I included that in my "further information". Any other ideas?– Jim DeLaHunt
46 mins ago
Thank you for this suggestion, and welcome to Unix & Linux Stack Exchange. Unfortunately, I think it does not apply to me. I already ran
cap_mkdb on both /etc/login.conf and ~/.login_conf. I included that in my "further information". Any other ideas?– Jim DeLaHunt
46 mins ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f538776%2fwhy-arent-my-login-conf-settings-respected-when-ssh-into-freebsd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown