rajkumar@plains.UUCP (A. Joseph Rajkumar) (02/19/90)
Hi netters
I am the sys-adm for a NeXt computer we have on campus. The problem
that I have been running into lately is that the 400-dpi laser printer
sometimes does not seem to want to print.
I have tried various things like running the "lpc" to enable printing
and spooling, going though the niload printcap etc, but every once in
a while the printer refuses to print at all.
On rebooting the system, then the printer starts going and later
on, I don't when it suddenly quits printing.
Have any of the NeXt users ever run into this problem, and if so
how did you fix it, or is it a strange hardware problem that we are
having.
BTW, when I log on to the NeXt from the console and finger to see
who is there on the system, it shows me twice, which is not what I
am concerned with, but one of it says idle time "in days". I am frustrated
and log-off and finger who is on that machine from some other machine, it
does not say that I am logged-on, but the next time, I log on from the
console, it shows me idling for days.
Have these problems being ever discussed before on the net, or is it
my stange problem. Any information or help will be greatly appreciated.
Joseph Rajkumar
email:- rajkumar@plains.nodak.edujpd00964@uxa.cso.uiuc.edu (02/20/90)
> BTW, when I log on to the NeXt from the console and finger to see >who is there on the system, it shows me twice, which is not what I >am concerned with, but one of it says idle time "in days". I am frustrated >and log-off and finger who is on that machine from some other machine, it >does not say that I am logged-on, but the next time, I log on from the >console, it shows me idling for days. Two problems here. You are probably logged in both the shell and the terminal. That means you are logged in twice. While the getty does update the wtmp file for log-ins, it does not update them for log-offs. This, unfortunately, means that the machine only knows you got on, not that you ever left. Michael Rutman #include <std.disclaimer>