Frequently Asked Questions.     Please read through this before you
				report a problem or bug. Thanks. :)


Questions 1-9 are runtime problems.
Questions 10+ are compile problems.

FIRST CHECK THAT:

NOTE, any problem that occurs while upgrading lightbar you should 
ALWAYS replace the new lb.conf with the old one or else you're bound
to have some problems...

Also make sure that all the files are in there correct places and you've
edited the 'config.h' correctly with the right settings and ran the 
configuration script.

Also make sure to read the comments in lb.conf CAREFULLY.

IF YOU STILL HAVE YOUR PROBLEM:

1) Q: When i execute "login -p" or "login -- <username>" from a shell to
   switch to another user no matter what account i try when i type in the
   correct password it returns "Password Incorrect" or "Login Incorrect" 
   when i'm not root.

   A: LightBar for security should never be +s'ed there for it cannot 
   switch users for you, this can also be caused because lightbar
   cannot read the /etc/shadow file because it's not being ran as root, if
   you need to switch users use 'su' instead of lightbar it's more
   effective or get onto a root account and execute /bin/login (or just
   exit out of the system and relogin as the user).

2) Q: Why's my terminal constantly screwed up?  Everytime a login from
      agetty it returns my $TERM as vt100 or dumb and my terminal is
      always screwed up!

    A: Your terminal settings are usually detected by lightbar by getting
       agetty's and or in.telnetd's input as far as term and different
       environment settings, if it doesn't work try upgrading your agetty.

3) Q: After i type in my username it seg faults!!

   A: ACHK! this is either 2 problems, it -MIGHT- be because your using
      glibc, (i'll beta test lightbar in the future with this library)
      bout i doubt it (just because glibc includes the same funtions as
      normal libc) but mind you it hasn't been beta tested with glibc.

      -BUT- This is also caused when lightbar isn't dynamically linked
      with libc.so.5 in /lib do 'ldd /bin/login' if it reports 'Statically
      linked (ELF)' then your screwed and you'll need to get a fresh 
      libc and compile the newest version (something in your libc got
      screwed up.. ) if it reportrs 'libc.so.5 => libc.so.5.X.XX' then
      read the README file on reporting bugs or problems and then just
      replace your safe login backed up /bin/login~ back to /bin/login
      and /usr/sbin/in.telnetd~ /usr/sbin/in.telnetd and you'll be 
      alright. :P

4) Q: The program segmentation faults (core dumps) or exits if there's
      a incorrect username and password.

   A: This happens with crypt() this is a problem in it's libc code
      and not with lightbar, a patch fixing this should be released
      sometime in june.  I talked with Mike Perry (s0nic) and he's 
      working on the bug :) be patient.


5) Q: I Get the message 'No utmp entry.  Please exec "login" from the 
      lowest level "sh"' when i type /bin/login to relogin or I run 
      xterm/rxvt or when i try to login with agetty.  What's wrong?

   A: This happens when lightbar isn't ran with the correct parameters
      by rxvt/xterm (funny this hasn't happened with xterms i've tested
      it with) but anyways, An easy way of fixing this with agetty is 
      replacing and installing the one in telnetd/ directory made when
      you type 'make'.  As for xterm rxvt try upgrading them they shouldnt
      use incorrect parameters, a correct way of running lightbar is:

		/bin/login -- [ username ] (with out the brackets)

      Just running /bin/login [ username ] or just /bin/login isn't
      correct /bin/login -- [ username ] tells lightbar to kill the
      environment create a new one for the specified username and just
      get the Password for the specified user and validate, etc.  Although
      /bin/login -p will store the environment correctly and do the login
      process the same as /bin/login -- [username].

6) Q: I get the error 'unable to determine your tty name.' 

   A: esh. your utmp/wtmp files are screwed up or the permissions on 
      /dev/ and /dev/tty* 's are incorrect check all of those things
      one of them must be broken.  OR your on a tty that isn't listed
      in the /dev/ fix this and you should be ok.

7) Q: None of my utmp works :\ when i run 'w' it just reports my username
      but no tty or idle information etc. 

   A: This really isn't a error with lightbar but i've experianced it
      before and is farely common, this is just when /dev/ is chmod'ed
      to only be readable by a certain user, just chmod a+rx /dev/ /dev/*
      and chown root.tty /dev and things should work again.

8) Q: When i run lightbar i get the error(s): 'Error: No password type was
      defined.  Recompile' or, 'Error: More than one password encryption
      type defined.  Recompile'.

   A: This is because you didn't run the ./configure script before
      compiling or atleast didn't run it correctly, make sure you answer
      the questions when running './configure' correctly, use the FULL
      names of encryption not just abbreviations.! Then recompile lightbar
      and it should be fixed.


9) Q: I get this error when login gets ran;
	'Warning: No configuration file exists: /etc/lb.conf: File not found.'
	'Initalizing backup login routine; Please contact the system administration.'

   A:  This means lightbar couldn't find where your configuratino file;
       lb.conf is located.  Simply copy a default lb.conf from the 'config'
       directory into the directory specified (usually /etc unless set other
       wise).  That should fix the problem.

10) Q: I get the error compiling lightbar with 'libwrap' ? What's wrong?

    A: ugh. You either need to recompile your tcp_wrappers package if it's
       a 'undefined reference' or if the library isn't found copy the one
       in the apps directory to /usr/lib and run 'ldconfig'.

11) Q: I get this error while logging in:
	"Error in /etc/limits: (line XX) mallformed limits entry."
	"1 error(s) detected while setting limits.  Contact your system administator"

    A: Your /etc/limits file is corrupt or you messed it up, look at the
       line it says your having the problems at and correct the error
       most of the time it's just a simple spelling mistake or something
       :P.  Also read the man page  limits(1) for more information or read
       the file 'lightbar.manual'. 
