Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Mar 2006 10:51:47 -0600
From:      "Christian S.J. Peron" <csjp@FreeBSD.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        Peter Jeremy <peterjeremy@optushome.com.au>, src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org
Subject:   Re: cvs commit: src/usr.sbin/syslogd syslogd.c
Message-ID:  <442D5E23.7010208@FreeBSD.org>
In-Reply-To: <20060331163221.Q88223@fledge.watson.org>
References:  <200603302104.k2UL4qF7086165@repoman.freebsd.org> <20060331080654.GB776@turion.vk2pj.dyndns.org> <20060331090421.I9972@fledge.watson.org> <442D475C.2030604@FreeBSD.org> <20060331163221.Q88223@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote:

>
> On Fri, 31 Mar 2006, Christian S.J. Peron wrote:
>
>> Although I agree this is a good idea, I think it would be more 
>> appropriate to place these kinds of checks in newsyslog(8) so that 
>> other programs logging can take advantage of this.
>
>
> The program generating the log message is presumably the one that has 
> to decide not to generate it if space is low.  Log messages currently 
> come from syslogd.  Are you actually suggesting that syslogd should 
> read the newsylogd.conf file to find settings?
>
> Robert N M Watson
>
>
>
No not necessarily,

Just that perhaps we should add a "This log file can only consume %X of 
the file system is resides on" and rotate the files possibly? I have not 
given it a great deal of thought as of yet. In any case, I am open to 
suggestions for this problem. I agree the feedback loop is not desirable.

I do know however that issues like mail spools temporarily filling up 
the file systems resulting in syslogd stop working is problematic.

-- 
Christian S.J. Peron
csjp@FreeBSD.ORG
FreeBSD Committer
FreeBSD Security Team




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442D5E23.7010208>