I am using Mandrake Linux and I am unable to login either in the graphical or the command line. In either situation the login acts like it enters the login then it just pops back, with no login failure. I have a database on the system my work needs desperatly.
I noticed threads mentioning vector, vasm,. I am not sure how to use these or what they are. I upgraded the system and that was no help. But if I reload the system and not partition i should sstill be able to get my database right?

Thanks,
DAn

Can you try to connect as another user?? and then su to root (without the -)

Else use a cd based linux like knoppix (needs a reboot though) and check the password file...

thanks for info. I am going to download knoppix and try that. Will I be able to figure out what it is doing? Do I go into the password file with vim?
Thanks again
DAn

The passwords file should tell you what is run for the user in terms of shell at boot. It could be a problem with the shell just quitting when its loaded I am not to sure.
Either way the Knoppix CD will allow you to atleast get your DB off the system if that is what you need.

First you have to mount the hard drive, than you can use a text editor like vim or gvim . Just make sure you also edit /etc/shadow.

You can also just create another root user, for example "rot" and make sure that you give it a " statically linked shell" like /bin/sh! And don't forget to remove it again once you have figured out the problem.

Good luck

I brought the drive over to another linux box I am working on to create my PDC. With the help of what I found in Mount HD Partition forum from David_Ross, I was able to mount the drive. Wahoo!! Do you know how to go about checking my passwd file through vim. What am I looking for?
Dan

Bit hard to guess from here but I would look for the location of the shell would be a good place to start, here is an example

root:x:0:0:root:/root:/bin/sh

(If you want to know what those fields mean do a "man 5 passwd")

Than make sure that the shell is "statically linked" by using the following command

file /bin/sh

Also check if the file /etc/nologin exists, if so remove it, however it existence should not prevent root from logging in..

If that al seems ok just have a look in /var/log
and see what the messages, syslog or authlog tell you

Good luck

Thanks
Well since I saved our data file I wasn't squimish to put the hd back in the original box. I reinstalled a full installation of Mandrake Linux 10 and what do you know same problem. This time though I walked away with it blinking login and when I came back I had this message.

Linuxapache:login application bug: crond(3495) has SIGCHLD set to SIG_IGn but calls wait().
(see the notes section of 'man2 wait'). Workaround activated.
Linuxapache:login application bug: crond(3495) has SIGCHLD set to SIG_IGn but calls wait().
(see the notes section of 'man2 wait'). Workaround activated.

Intersting huh? Wow what fun. well into man2 we go.

Dan

I had the same error message on my box when I had a problem with Fedora CORE1, i looked and the only way I found to fix it was a reformat and reinstall because to many packages were messed up, it was right after I did an Up2date.
But I don't know what you will do since you just installed.

I agree with you I am doing that as I write this.