Hamish Moffatt wrote:
On Tue, Jun 28, 2005 at 07:57:43PM -0500, Kevin Kuphal wrote:
Except the script would tend to get complicated in disk full situations
where Myth already has much of the functionality built in for that, it
only needs to understand that RecordFilePrefix can be something other
than a single value from the settings table. Plus, this opens the door
for a wide range of features related to disk management that can enhance
the product.
How would it know whether a particular location has sufficient disk
space for a scheduled recording?
How does it know now? If Myth already has a mechanism to deal with
full disk situations, it will work regardless of where the recording is
destined, as long as it is checking the appropriate location for free
space. Again, this is one of there areas that could be enhanced by
multiple locations in that if the default location for particular
recording is full, Myth could be instructed to make various decisions on
whether to expire content from the drive or simply record in a different
location.
Kevin
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
