Bug 220839 - Locale not being set from login.conf.db
Summary: Locale not being set from login.conf.db
Status: Closed Feedback Timeout
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 10.3-RELEASE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-18 19:29 UTC by MMacD
Modified: 2020-12-02 23:01 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description MMacD 2017-07-18 19:29:08 UTC 
To get thousands separators in file sizes, I added values (0x2C) for thousand_sep and thousep in /etc/login.conf, and called cap_mkdb to update the db.

Inspection of /etc/login.conf.db showed that those vars were now defined.

But when I logged in again and called locale -k, the values were again/still the empty string.

Even saving a copy of login.conf as ~/.login.conf, per the docs, and cap_mkdb'ing there, too, made no difference.

Apparently there's some locale data hardcoded somewhere that's being used, while the config files and their databases are being ignored.
Comment 1 Yuri Pankov freebsd_committer freebsd_triage 2018-11-16 23:03:35 UTC 
Where is it documented that keywords in login.conf override the locale data?  I can't find anything related in the code and/or documentation.