Gerhard Damerau napisał(a): > Tomasz, > We habe the same idea but we do not use identd but pam_auth with > squid/squidguard. (We use SuseLinux 8.2) > You will receive every information about usernames and clients in > access.log. If you understand German, then have a look at > www.linuxbu.ch > Kapitel 13, Abschnitt: "Benutzer authentifizieren"
Chapter 11 ;) Thank you very much. I looked into this book and realized that user has to authenthificate himself/herself with his/her password, right? I mean: user know the password, some window shows, user enters username/password and he/she can surf then. I don't want to give users any passwords, because each of my terminals has its own user. Example: terminal ws001 - user opac001, ws002 - opac002, ..., ws011 - oin001, ws012 - oin002. If I turn on terminal, user is logged in automatically. So, I would rather have solution like this: Squid "knows" users (from entry in squid.conf) and is using identd for recognizing incoming connections from different users. The problem is: I don't know how to fire up ident clients on terminals. Ident daemon is running on LTSP server. Can anyone help me or give some helpful hints? -- Tomasz Lewicki PGP key: http://stalker.republika.pl/stalker.asc
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
