On Friday 27 July 2001 08:47, etharp wrote:
> well, we can look at the logs, if you want, or we could create a new user
> from the text prompt, and see how it logs in.
per this suggestion, I pulled /var/log/syslog and compared a failed login to
a good one, and see one difference. Below are the last few lines from a
failed login. I have more if we need them:
Jul 28 06:55:34 localhost modprobe: modprobe: Can't locate module char-major-4
Jul 28 06:55:38 localhost last message repeated 35 times
Jul 28 06:55:38 localhost modprobe: modprobe: Can't locate module
char-major-180
Jul 28 06:55:40 localhost last message repeated 24 times
Jul 28 06:56:47 localhost modprobe: modprobe: Can't locate module binfmt-0000
Jul 28 06:57:03 localhost last message repeated 3 times
On a successful login, "localhost modprobe: modprobe: Can't locate module
binfmt-0000" is repeated only two times, then I get the same messge for a
collection of sound-* modules. The "can't find char-major-*" message repeat
the same number of times regardless of whether the login works or doesn't.
Meanwhile, I am successful in logging in via console mode if I do a 'restart
in console mode'.
Incidentally, the failed login has gone from the previous exception to the
rule, to where I have to make multiple attempts, including powering down, to
get signed in.
I did reinstall my printer last night, and fixed my halt problem per someone
else's documentation here. I assume the "now it is safe to turn off your
computer" is a windoze specific message, since I never see that. I get to a
message saying that the system is stopped after what seem to be all the
shutdown messages complete ok.
>
> On Friday 27 July 2001 09:05, root wrote:
> > On Friday 27 July 2001 04:43, etharp wrote:
> > > is this while you wait to login? have you installed mandrake security
> > > and what level? (paranoid?) or a firewall? what reaction are you
> > > expecting?
> >
> > i was expecting no reaction, since I had never heard of that method of
> > logging on before. I hit alt-f4 at the point where otherwise I would
> > enter root and my password and hit go.
> >
> > The original problem when attempting to login via the normal login panel,
> > I sometimes was bounced back to the login panel without getting logged
> > in, and when that happened had to reboot before being successful at
> > logging in.
> >
> > When installing, I took the defaults for security and the firewall.
> > Before altering those, I'll want an explanation of why the bounce occurs
> > only some of the time instead of every time. It seems to me if it was a
> > security or firewall problem, the bounce would be consistent instead of
> > sporadic.
> >
> > > On Friday 27 July 2001 00:48, root wrote:
> > > > On Thursday 26 July 2001 16:34, etharp wrote:
> > > > > what happens if you hit ctrl+alt+f4 (or any other f-key up to f6)
> > > > > and log in?
> > > >
> > > > nothing. no reaction at all
> >
> > --
> > "Gentlemen, it's in beta. That means it's like Windows. They're letting
> > you test it while they continue to screw it up until it's totally
> > useless." (Bigg Fredd in RCC talking about Google's temporary interface
> > to the deja archives)
--
--
"Gentlemen, it's in beta. That means it's like Windows. They're letting you
test it while they continue to screw it up until it's totally useless."
(Bigg Fredd in RCC talking about Google's temporary interface to the deja
archives)
