On Wed, Dec 14, 2005 at 05:01:27PM -0500, Isaac Richards wrote: > I don't see how that's any different than just autoexpiring things, though. > As long as the backend is running and the user has not individually disabled > autoexpire for every recorded program, the disk will never be completely > full.
If I correctly apprehend the issue, I see two potential problems, of differing import: 1) If the disk is full of live recordings which will conviently expire to get out of the way of more important stuff, then you'll never know how much free space you really have. Myth could, I suppose, do the math internally for it's own display, but being able to use something as lightweight as df(1) has it's advantages. (cron scripts, for example). 2) depending on how far in advance the programs are expired, and what OS/filesystem is in play, the delete itself may take a notable amount of processor horsepower, increasing the minimum requirements of the system. Cheers, -- jra -- Jay R. Ashworth [EMAIL PROTECTED] Designer Baylink RFC 2100 Ashworth & Associates The Things I Think '87 e24 St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274 "Space is called 'space' because there's so much *space* there." - John Walker, of Fourmilab, on Trek's End
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
