OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: David M. Fetter (dfetter_at_setec-astronomy.biz)
Date: Mon Jan 27 2003 - 04:04:23 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Did you have some sort of backups running? If not, I doubt you will be
    able to recovery it. If you don't have any backups running but do have
    a tape drive, you could try using my simple backup script I wrote. It
    has worked well so far for simple single system uses. You can download
    it at http://www.setec-astronomy.biz/resource.htm.

    Alternatively, have you tried reading the passwd and shadow files? Is
    the use data missing or is it simple totally garbled data? Perhaps the
    /etc filesystem (if it's on a separate filesystem) didn't mount properly
    after the fsck and you need to mount it. You also may have backup
    passwd and shadow files that were automatically created by SuSE from a
    patch or sorting. They are generally named something like passwd-,
    passwd.YaST2save, passwd.backup where the appropriate shadow file
    counterpart has the same ending.

    ΚΑΡΑΘΑΝΑΣΗΣ ΔΗΜΗΤΡΗΣ wrote:
    > Ηi. I am running suse linux 7.1 with sendmail, dns, mysql ..! I have a
    > big problem. Yesterday I reboot my machine but when is starts it tells
    > me to do fschk.ext2 manually. I did it. I reboot the machine, all the
    > services went up but I can't login. The mail also prompts for incorrect
    > password!!!! It looks like the /etc/passwd file corrupts!!!!! Is there a
    > way to recover it. Please help. Is urgent!!!!
    >
    >

    -- 
    David M. Fetter (MegaSurge) - http://www.setec-astronomy.biz/
    

    "The world is full of power and energy and a person can go far by just skimming off a tiny bit of it." Neal Stephenson - Snow Crash

    -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-helpsuse.com Security-related bug reports go to securitysuse.de, not here