Thanks for your quick response. What about the $prefix/var/nessus/<user>/sessions/<scanid>-index file? Also, what would be the actual procedure for resuming the scan? Can I just do a "restore session" and have the server resume a detached scan?
At 10:39 PM 4/25/2002 +0200, Renaud Deraison wrote: >On Thu, Apr 25, 2002 at 10:30:34AM -0500, John McCain wrote: > > I had a detached scan running against a network, and the scan was > > interrupted by what began as poor connectivity, but then progressed to an > > outage. This means I've got X amount of good data before the problem > began > > (about 30 hours worth) which I'd like to preserve, Y amount of data whose > > quality is suspect because of the connectivity issue, and a scan which was > > shut down. > > > > If I have a certain time in mind after which the data is to be thrown out, > > is there any way to manually manipulate the session files to eliminate > this > > data? Then, is there a way I can resume the scan where it left off? > >You can edit $prefix/var/nessus/<user>/sessions/<scanid>-data and remove >the hosts whose data is suspect (you can correlate that with >nessusd.messages to find which host was being tested at which time). > > > -- Renaud
