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. 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? On Tue, Dec 3, 2013 at 10:20 AM, Erik Anderson <erikerik at gmail.com> wrote: > On Tue, Dec 3, 2013 at 10:12 AM, Ryan Coleman <ryanjcole at me.com> wrote: > >> Is there a way to reset this without rebooting the server every 60 >> minutes? > > > 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. > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > -- -Shawn -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20131203/ff50d09f/attachment.html>