On 06/08/10 23:48, Wayne Stallwood wrote:
On 06/08/10 22:13, David Reynolds wrote:
Check that the machine can resolve DNS. I've seen quite big delays in logging in and especially when using sudo when a machine has unreachable/unresponsive DNS servers.
AFAICS, DNS is working OK. I can ping and tracert.
Yes that will cause problems, Also look at the pam.d configuration.
Specifically which modules are optional and which are required in the login config file.
Sorry, loads of files in pam.d - which one is the login config file? anyway, reading comments in file "common-password", it mentions using pam-auth-update to manage selection of other modules. I ran this and found that log-in via NT domain was enabled, which is not what I want to do, as this machine is the server, there are no windows servers. I disabled that option, and tried it, but it didn't seem to make a difference. :-(
Were you using anything funky for samba authentication and some automated way of setting it up (i.e using swat)
No, manually edited config file Will check it.
to set up something like winbind to authenticate samba against a Windows Domain ?
Hopefully not!
As that can and will mess with pam authentication. Is it possible that you enabled this configuration by mistake ?
Absolutely possible, but don't know how if I did.
Also is SELinux installed as ISTR that can hook into pam and a problem there could be causing a delay.
SELinux not installed, AppArmour is installed I think though.
Thanks for your help so far. Will keep plugging away! Cheers Steve