Re: Sources of changes to /etc/motd and of other login messages?

[Lloyd Zusman <ljz@asfast.com>]

Colin Watson <cjwatson@debian.org> writes:

> On Thu, Dec 12, 2002 at 03:54:46PM +0100, martin f krafft wrote:
>> also sprach Colin Watson <cjwatson@debian.org> [2002.12.11.1244 +0100]:
>> 
>> PAM:
>> 
>> %> grep lastlog /etc/pam.d/login
>> session    optional   pam_lastlog.so
>
> He said he'd added the 'silent' option, though, in the original post.
>
> This isn't via ssh, is it? There's a bug filed about this, #169938.

Actually, it *is* via ssh.  About an hour ago I wrote a reply to Martin
Krafft here, saying that that the problem occurred both in login and ssh
... but I was wrong about login.  I came back here to correct that post,
and I just noticed this message of yours.

I just checked bug 169938, and on the basis of that report I set
"PrintLastLog no" in /etc/ssh/sshd_conf.  That fixed the problem.

I suppose that recompiling ssh with "--without-lastlog" might also have
done the trick (as long as I also make sure that I use "--with-pam").

I got thrown off the track when I mistakenly thought that I saw this
same problem when using 'login' as well as 'ssh'.

Martin Krafft's question a little earlier today got me thinking that I
had better double-check this, and I'm glad I did.

Thanks to the both of you.

Problem solved.  I'm happy.  :)

-- 
 Lloyd Zusman
 ljz@asfast.com