On Wednesday 28 March 2007 12:52, STeve Andre' wrote:
> I have a -current system thats working just fine as a web
> server. Everything is working as it should, save for updating
> the wtmp for logins.
>
> The last entry in the wtmp was the reboot for going live--
> since then logins work as expected but there is no record
> of them.
>
> Suggestions as to what to look for, to fix this? File perms
> aren't a problem, and nothing seems unusual to me. This
> is a -current system compiled on March 14th.
>
> Thanks,
>
> --STeve Andre'
Now that's weird...
Note: getting output to format correctly means shutting off
forced line wraps at 72 col
What is the output of last(1)?
# last
root ttyp5 :0.0 Sun Mar 25 19:33 still logged
in
jcr ttyC0 Sun Mar 25 11:16 still logged
in
reboot ~ Sun Mar 25 11:15
shutdown ~ Sun Mar 25 11:13
The above is accurate on my 4.0-stable system, since at the
moment I'm logged in and have a root shell going.
The part you might find odd is this:
# ac -p
root 68.36
total 68.36
Or more accurately:
# ac -p jcr root
root 68.37
jcr 0.00
total 68.37
In short, the "weird" part is just telling me that newsyslog(8)
is doing it's job properly, so ac(1) is not finding the login info
for the 'jcr' session which started days ago. See the notes in
ac(1) man page about updating the weekly(8) script to provide
user accounting information.
And yes, it is dumb to leave logins sitting around like I do but
this particular test machine is physically secure and regularly
scrapped and rebuilt.
jcr
