<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 14 Dec 2005, at 20:42, James Armstrong wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I also have this problem. The logs are created, but when they too big I delete them and they are not recreated until I restart Asterisk.</DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Ah, is this the old unix quirk, where removing a directory entry does not remove the associated</DIV><DIV>file, because a program still has it open ? (it used to be a great way to hide big files from </DIV><DIV>sysadmins :-) )</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If I have this right, then asterisk still has an open file handle to the logfile, and is</DIV><DIV>blissfully unaware that you have removed the last link to it in the filesystem.</DIV><DIV>The kernel won't release the file until all the file handles and directory entries</DIV><DIV>to it have gone - which happens when you shutdown asterisk.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>You should be able to spot of this is the case by listing the open files associated with the</DIV><DIV>asterisk process (or looking in /proc/$asterisk_pid/fd)</DIV><BR><BLOCKQUOTE type="cite"> </BLOCKQUOTE></DIV><BR><DIV> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><A href="http://www.westhawk.co.uk">http://www.westhawk.co.uk</A>/</FONT></P> </DIV><BR></BODY></HTML>