The value for me adding the link at the tail end of the conversion was that I knew we could watch the show once the name became visible. We use Logitech Revues as the frontend and since it has a handy browser we can now delete the show from Mythweb. Having the cronjob run every 10 minutes seems to keep everything tidy. <div>
<br></div><div>Thanks everyone for your comments and suggestions.<br>
<br><div class="gmail_quote">On Wed, Feb 8, 2012 at 2:52 PM, Jeremy Jones <span dir="ltr"><<a href="mailto:jeremy.dwain.jones@gmail.com" target="_blank">jeremy.dwain.jones@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>On Wed, Feb 8, 2012 at 10:56 AM, Zarthan South <<a href="mailto:zarthan@gmail.com" target="_blank">zarthan@gmail.com</a>> wrote:<br>
><br>
> I have used mythlink as a cronjob and like you ran it once a night. I started adding it to the tail end of my job when I started plugging my converted recordings back into the database. It seemed like the thing to do ;) Since I play the recordings from the link name I was concerned that it might case playback issues if a generic mythlink run happened during playback. My conversion from mpeg2 to mp4 only takes 5 or 6 minutes for a half hour program so a recording is ready very quickly and we often want to watch them. Turns out a mythlink run doesn't have any effect at least so far and I just created a cronjob to run every 10 minutes.<br>
><br>
> It doesn't seem to have any effect.<br>
><br>
><br>
<br>
</div>I probably should have been more clear. I run mythlink as a userjob,<br>
specifying the recording (specify the --chanid and --starttime<br>
arguments), which only adds the link for that one recording. Then I<br>
run it again as a nightly cron job that deletes an re-creates all<br>
links, so as to get rid of orphaned symlinks due to a deleted<br>
recording. Looking back, I see you are the OP on this thread; so glad<br>
you got it working. If your recording library grows and it does start<br>
to be an issue, you may want to try my setup. Also, there is a way to<br>
run as a system event, but I would suspect that would be to create the<br>
new symlink upon the start of a recording, instead of upon the<br>
deletion as you were wanting to do in your OP.<br>
<br>
The only drawback I can see to running as a userjob to add the link<br>
and then again as a cron job to clean up the orphaned links, is that<br>
occasionally someone might attempt to play a file that was actually<br>
deleted earlier that day.<br>
<br>
I haven't heard a complaint at my house yet though :)<br>
<span><font color="#888888"><br>
Jeremy<br>
</font></span><div><div>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>
</div>