Renaud, I posted that info at 10:22. Here it is again:
> Do a 'ls -l all-2.0.tar.gz' and send us the results please, as well as > the md5 of the tar file you're getting. Thank you for the quick response. For the last scheduled update (1:00 a.m. this morning), The directory created was: drwx------ 2 root root 4096 Sep 2 01:05 nessus-update-plugins-20505 And the files in the directory are: -rw------- 1 root root 1025 Sep 2 01:05 all-2.0.sig -rw------- 1 root root 3558561 Sep 2 01:05 all-2.0.tar.gz -rw------- 1 root root 56 Sep 2 01:00 all-2.0.tar.gz.md5 The file all-2.0.tar.gz.md5 contains: MD5 (all-2.0.tar.gz) = b9d6daad3c00f6d5a01df084b75c9e42 When I run md5sum on all-2.0.tar.gz myself, I get this: caa2abefa52659b7cd124a1a5c94419c all-2.0.tar.gz John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Renaud Deraison Sent: Friday, September 02, 2005 10:48 AM To: [email protected] Subject: Re: Problem with nessus-update-plugins. On Sep 2, 2005, at 19:43, anon anon wrote: > What times are the plugin tar's updated? (GMT) The tar files are moved, not created on the fly (ie: tar -zcvf /tmp/ foo.tar.gz, mv /tmp/foo.tar.gz $location/all-2.0.tar.gz) <rant> If I could get an answer about the file size of all-2.0.tar.gz, we could diagnose if the problem is a network connection or something else. Of course, for the last weeks, every time I've tried to debug any issue I've been met with a dead silence from the party complaining about a given bug (except one or two notable exceptions). </rant> -- Renaud _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
