Date: Sat, 27 Oct 2001 18:30:09 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: tlambert2@mindspring.com, Mike Barcroft <mike@FreeBSD.ORG> Cc: hackers@FreeBSD.ORG Subject: Re: syslogd and kqueue Message-ID: <p05101005b800e4c90608@[128.113.24.47]> In-Reply-To: <3BDAFD1C.B7BF7ED4@mindspring.com> References: <20011026233957.A9925@parhelion.firedrake.org> <20011026200436.A61058@xor.obsecurity.org> <20011027043342.A18231@parhelion.firedrake.org> <20011027001704.B2586@coffee.q9media.com> <3BDAFD1C.B7BF7ED4@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:29 AM -0700 10/27/01, Terry Lambert wrote: >Mike Barcroft wrote: > > I recommend using newsyslog(8) for rotating log files. > >I recommend _NOT_ using newsyslog for rotating files. > >The problem is that newsyslog doesn't "rewrite history". >As an example, say you have [...] >Now you can only rotate it out with another 10K of data >writtent to an already full /var (other log files are now >free to consume the 10K you freed up), and then it will >take 5 log rollovers before your /var is down to its >proper disk utilization again, and your system is back >to normal... and these can never happen. >Until newsyslog is fixed to not be able to stage a >denial of service attack against you, I really, really >recommend against its use. Seems like it would be more user-friendly (to freebsd users in general) to fix newsyslog, instead of just telling people that they should not use it... If people "just don't use" newsyslog, how does that guarantee that whatever they do use will not have the same problem that you described? -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101005b800e4c90608>