| View previous topic :: View next topic |
| Author |
Message |
ninja
n00b
Joined: 17 Apr 2002
Posts: 26
Location: Melbourne, Australia
|
 Posted: Mon Nov 11, 2002 11:34 pm Post subject: configuration error msg on login |
 |
|
hi i did an emerge --update system last night then when i logged in this morroning i got these error messages as soon a i typed the user name
| Code: |
configuration error -unknown item 'CONSOLE' (notify administrator)
configuration error -unknown item 'DIALUP_CHECKS_ENB' (notify administrator)
configuration error -unknown item 'ENV_HZ' (notify administrator)
configuration error -unknown item 'ERASECHAR' (notify administrator)
configuration error -unknown item 'KILLCHAR' (notify administrator)
configuration error -unknown item 'LOG_OK_LOGINS' (notify administrator)
configuration error -unknown item 'MAIL_CHECK_ENAB' (notify administrator)
configuration error -unknown item 'MAIL_DIR' (notify administrator)
configuration error -unknown item 'NOLOGINS_FILE' (notify administrator)
configuration error -unknown item 'PORTTIME_CHECKS_ENAB' (notify administrator)
configuration error -unknown item 'QUOTAS_ENAB' (notify administrator)
configuration error -unknown item 'SU_NAME' (notify administrator)
configuration error -unknown item 'SU_WHEEL_ONLY' (notify administrator)
configuration error -unknown item 'SYSLOG_SG_ENAB' (notify administrator)
configuration error -unknown item 'SYSLOG_SU_ENAB' (notify administrator)
|
I'm pretty sure these are variables in a config file my question is which file/s and what would be good values? I'm running a very basic system at the moment i haven't emerged to much just fluxbox and opera really. |
|
| Back to top |
|
 |
masseya
Bodhisattva
Joined: 17 Apr 2002
Posts: 2602
Location: Baltimore, MD
|
| Posted: Tue Nov 12, 2002 4:52 am Post subject: |
|
|
This happened after you typed the user name and before you got a password prompt?
If you actually, got a password prompt and logged in then this is probably exactly what you said - an error in one of your configuration files. You can probably just grep for the variables on all the files in your configuration directories to try and find the offending script. That would help in figuring out how it happened.
For example: | Code: | | bash $ grep -l "VARIABLE" * |
while in /etc or some other configuration directory.
_________________
if i never try anything, i never learn anything..
if i never take a risk, i stay where i am.. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Tue Nov 12, 2002 5:20 am Post subject: |
|
|
I've seen this one before. See problems with a fresh G1.2 install.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
Ethernal
Tux's lil' helper
Joined: 06 Nov 2002
Posts: 106
Location: Stockholm, Sweden
|
| Posted: Tue Nov 12, 2002 8:25 am Post subject: |
|
|
I got that error when I opened a new tty, but only once. Never had it again
_________________
Hmm.. Of course, these are MY opinions - likely to be just as flawed as anyone else's. Um, really, I guess you should assume everyone's speaking out of some external influence. Believe in whatever makes sense to you. |
|
| Back to top |
|
|
|
Other Things Gentoo
