<snip>
> >running, as "echo test > file" won't work if the disk is
> >full. So...be cautious turning Nessus loose on your own
> >LRP box. :)
>
> I think this is a problem. I believe the ramdisk shouldn't fill up under
> any circumstances. Can we change log rotate to trigger on file size in
> addition to periodically?
>
It's got the ability in multicron, but commented out by default. I
haven't formally tested it, but it seemed to worked on my old low-memory
router. Still, a check every few minutes to start action seems like a
kludgy way to handle it.
> > Makes me wonder though. At the start of the scan,
> >/var/log/syslog, messages and kern.log were 15k, 13k, and
> >13k respectively. After the scan...all *three* of them were
> >over 980k before I ran out of disk space.
> > Sure, a brute-force DOS attack but...what am I doing
> >wrong where each packet log gets recorded in 3 places?
> >
> > Also...I noticed my cable-modem connect thru the LRP
> >was sluggish after the disk was filled. I checked with
> >www.bandwidthplace.com/speedtest and it confirmed: 671 kpbs
> >with a full disk, and 1293 kbps immediately after a reboot.
> >Perhaps the next time someone on the LRP lists mentions
> >that their LRP box is "acting slow" we should ask if they
> >recently unleased Nessus on it.
>
> That's strange.
>
> --
> Mike Noyes <[EMAIL PROTECTED]>
> http://leaf.sourceforge.net/
>
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-devel
>
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
