Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1213029" data-attributes="member: 82144">Hello and welcome <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Yes and yes.Size doesn't stop you from configuring a larger disk quota.The answer depends what the &quot;keep until...&quot; configuration is.If it's &quot;keep until... always&quot;, the recording will never be automatically deleted. Obvious. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />If it's &quot;keep until... watched&quot;, the client (ie. KODI in your case) is responsible for deleting it after you finish watching it. The enables the client to define &quot;watched&quot; in whatever way you prefer. For example, a movie might be considered watched and deletable at 85 to 90% viewed because you skipped the credits.If it's &quot;keep until... space needed&quot; (the default), that ties into the disk quota functionality. As you said, the server should automatically start deleting the oldest recordings which are marked &quot;keep until space needed&quot; once the space threshold/quota is reached.If it's &quot;keep until... date X&quot;, the server should automatically delete it when the date arrives.All this assumes that the user account that TV Server is using (usually a system account) has the requisite permissions for deleting files on the share.[edit: Recordings inherit the &quot;keep until...&quot; and &quot;keep until date&quot; values from the associated schedule that triggers them. The default &quot;keep until...&quot; is &quot;...until space needed&quot;. Changing a schedule's settings after it has been created will not affect recordings that were triggered/created before you changed the settings (hope that makes sense). Maybe this is what's tripping you up.]Further insight may be possible if you would provide your TV Server log files.Regards,mm</blockquote>

[QUOTE="mm1352000, post: 1213029, member: 82144"] Hello and welcome :) Yes and yes. Size doesn't stop you from configuring a larger disk quota. The answer depends what the "keep until..." configuration is. If it's "keep until... always", the recording will never be automatically deleted. Obvious. :) If it's "keep until... watched", the [B]client [/B](ie. KODI in your case) is responsible for deleting it after you finish watching it. The enables the client to define "watched" in whatever way you prefer. For example, a movie might be considered watched and deletable at 85 to 90% viewed because you skipped the credits. If it's "keep until... space needed" (the default), that ties into the disk quota functionality. As you said, the server should automatically start deleting the oldest recordings which are marked "keep until space needed" once the space threshold/quota is reached. If it's "keep until... date X", the server should automatically delete it when the date arrives. All this assumes that the user account that TV Server is using (usually a system account) has the requisite permissions for deleting files on the share. [edit: Recordings inherit the "keep until..." and "keep until date" values from the associated schedule that triggers them. The default "keep until..." is "...until space needed". Changing a schedule's settings after it has been created will not affect recordings that were triggered/created before you changed the settings (hope that makes sense). Maybe this is what's tripping you up.] Further insight may be possible if you would provide your TV Server log files. Regards, mm [/QUOTE]

Verification