On Thu, 2008-04-03 at 12:06 -0500, Martin McCormick wrote:
> I noticed that every sudo command I issue is accompanied
> by a "Last login" message.
>
> 25testokcns root $ls .hushlogin
> ls: .hushlogin: No such file or directory
> 26testokcns root $sudo touch .hushlogin
> Last login: Thu Apr
> The commands always work but I would rather not get that message
> each time. Am I missing something obvious?
A quick google search will show you that it's the
${LOCALBASE}/etc/pam.d/sudo file which is the root of your "problem".
It's pam_lastlog(8) which makes the message. If you don't need it
Steven Friedrich writes:
>> 26testokcns root $sudo touch .hushlogin
>Well, it IS odd that you're using sudo when logged in as root 8o)
I was cd'd to the /root directory, but was logged in as
me. It kind of got me there for a second, but notice the $ in
the prompt.
Interestingly en
On Thursday 03 April 2008 01:06:37 pm Martin McCormick wrote:
> I noticed that every sudo command I issue is accompanied
> by a "Last login" message.
>
> 25testokcns root $ls .hushlogin
> ls: .hushlogin: No such file or directory
> 26testokcns root $sudo touch .hushlogin
> Last login: Thu Apr
I noticed that every sudo command I issue is accompanied
by a "Last login" message.
25testokcns root $ls .hushlogin
ls: .hushlogin: No such file or directory
26testokcns root $sudo touch .hushlogin
Last login: Thu Apr 3 11:38:24 from testokcns.osuokc
27testokcns root $sudo date
Last login
