Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: /var/log/* deleted
- To: tlug@example.com
- Subject: Re: /var/log/* deleted
- From: SL Baur <steve@example.com>
- Date: 26 Jan 2001 17:07:12 +0900
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: "Stephen J. Turnbull"'s message of "Thu, 25 Jan 2001 19:48:25 +0900"
- Mail-Copies-To: never
- References: <006901c086c2$735e2120$6f04030a@example.com> <14960.1145.398879.683086@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <sGjvQC.A.FZ.pATc6@example.com>
- Resent-Sender: tlug-request@example.com
Stephen J Turnbull <turnbull@example.com> writes in tlug@example.com: ... > Then you can try midnight commander; it's supposed to be able to > undelete ext2 fs files. if that doesn't work, you could go at the > raw device with Python or Perl, extracting things that look like logs > of connections. The utility to use is debugfs. If you can locate the correct inode, you can manually reset the deleted flag. After a later fsck, the file will reappear in lost+found. This will only work if the filesystem has been relatively quiet since the file deletion, but it _will_ work if you're lucky.
- References:
- /var/log/* deleted
- From: "Mustiantono" <simus@example.com>
- /var/log/* deleted
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: Despair.com trademarks :-(
- Next by Date: Re: Despair.com trademarks :-(
- Prev by thread: /var/log/* deleted
- Next by thread: Despair.com trademarks :-(
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links