File system full
keramida at ceid.upatras.gr
Wed Oct 18 14:35:43 UTC 2006
On 2006-10-18 14:34, Matthew Seaman <m.seaman at infracaninophile.co.uk> wrote:
> Giorgos Keramidas wrote:
> > The file `alias.log' is not rotated by `newsyslog.conf', so maybe we
> > should add it there? Then we can let `newsyslog' signal `natd' by:
> > %%%
> > diff -r 4474abb9619a etc/newsyslog.conf
> > --- a/etc/newsyslog.conf Fri Oct 13 17:34:54 2006 +0300
> > +++ b/etc/newsyslog.conf Wed Oct 18 15:54:52 2006 +0300
> > @@ -18,6 +18,7 @@
> > #
> > # logfilename [owner:group] mode count size when flags [/pid_file] [sig_num]
> > /var/log/all.log 600 7 * @T00 J
> > +/var/log/alias.log 600 7 100 * JC /var/run/natd.pid
> > /var/log/amd.log 644 7 100 * J
> > /var/log/auth.log 600 7 100 * JC
> > /var/log/console.log 600 5 100 * J
> > %%%
> > Can you please add this line to your newsyslog.conf file and let it run
> > for a while to see if it prevents the `alias.log' file of `natd' to fill
> > your /var/log filesystem?
> > I don't use `natd', so I can't test this myself for a long enough
> > period.
> natd doesn't do the close and re-open all filehandles thing on receipt
> of SIGHUP which pretty much makes it unsuitable for use with newsyslog.
> (SIGHUP is caught by natd, but the only thing it does is cause natd to
> update its idea of what the IP address is on the nat'ed interface.)
> There doesn't seem to be any signal that you can send natd with the
> usual 'reread all config files and re-open all file descriptors'
> effect that most daemons understand.
That's probably a bug, then, I guess. The fact that natd can keep a
file open for an arbitrary amount of time and keep appending to it,
until either natd dies or the file fills up an entire partition is not
really a good idea :(
I'll open a PR for this, and see if the people more knowledgeable with
natd's internals can help with the SIGHUP-triggered actions of natd.
More information about the freebsd-questions