<div dir="ltr">You can't delete an open file and expect the size to be freed up. You either need to simply zero the file by catting /dev/null into it (not recommended for historical purposes), or rotate the logs. Look into logrotate, it'll resolve your problems.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 3, 2013 at 10:29 AM, Ryan Coleman <span dir="ltr"><<a href="mailto:ryanjcole@me.com" target="_blank">ryanjcole@me.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">It was a hack attempt in the first place - a simple delete… but I could add restart of apache into the mix… maybe that will resolve it?<div>
<div class="h5"><div><br><div><div>On Dec 3, 2013, at 10:27 AM, Shawn Fertch <<a href="mailto:sfertch@gmail.com" target="_blank">sfertch@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><div>This is more of a hack solution, and doesn't do anything to resolve the real issue. It sounds more like the file is open, and being deleted, which doesn't remove the inodes.<br>
<br></div>How is the log file being cleaned out? Zeroing it, logrotate, or some other method? Does the application need to be bounced briefly, or would simply zeroing the file do the trick? <br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 3, 2013 at 10:20 AM, Erik Anderson <span dir="ltr"><<a href="mailto:erikerik@gmail.com" target="_blank">erikerik@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 3, 2013 at 10:12 AM, Ryan Coleman <span dir="ltr"><<a href="mailto:ryanjcole@me.com" target="_blank">ryanjcole@me.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there a way to reset this without rebooting the server every 60 minutes?</blockquote></div><div class="gmail_extra">
<br></div>A umount/mount cycle on that fs will typically clear out this sort of thing. *If* you keep your logs on a separate fs (which everyone *should* be doing) it's faster than a reboot, but obviously not ideal, as it may require a bit of downtime each cycle.<br>
<br></div></div>
<br>_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>-Shawn<br><br><br>
</div>
_______________________________________________<br>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br><a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br><a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>-Shawn<br><br><br>
</div>