On Sun, Jan 11, 2009 at 3:14 AM, Mike Perkins <span dir="ltr"><<a href="mailto:mikep@randomtraveller.org.uk">mikep@randomtraveller.org.uk</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Michael T. Dean wrote:<br>
> On 01/10/2009 07:56 AM, Bill Williamson wrote:<br>
>> I have a mythbox hooked up to a projector and an SDTV. I use it for<br>
>> one OR the other each time. The settings for each setup are wildly<br>
>> different. I've separated them thus far by using a custom identifier<br>
>> (theater-TV and theater-PROJ) to keep settings apart (lots of myth<br>
>> settings differ to get best picture).<br>
>><br>
>> Right now I have<br>
>> -a mysql.txt for each one in ~/.mythtv that is identical apart from<br>
>> the custom identifier line<br>
>> -a shell script to start each "mode" (cp ~/.mythtv/mysql.txt.proj<br>
>> ~/.mythtv/mysql.txt; mythfrontend)<br>
>><br>
>> Is there a way to pass which identifier to use into mythfrontend? It<br>
>> seems like it'd be a much better way of doing so. The man page<br>
>> mentions overriding specific settings with a flag, but I couldn't get<br>
>> it to work fro the master identifier (only for other specific settings).<br>
><br>
> The -O override-setting option is really meant for changing one or two<br>
> settings on one-shot runs. It only works for settings in the settings<br>
> table. The custom identifier, however, is used as the "hostname" for<br>
> all settings pulled from the settings table. Therefore, I don't think<br>
> it's possible to change the custom identifier at the command line.<br>
><br>
> The closest thing would be changing the location of the configuration<br>
> directory (using a not-highly-publicized environment variable), but that<br>
> would mean maintaining two otherwise-identical copies of what's<br>
> currently in ~/.mythtv. (And, yes, while you could use links for the<br>
> equivalent content, when doing so it's likely that over time something<br>
> would get changed in one and not the other, and it would require careful<br>
> creation of all the directories that Myth would normally create over<br>
> time under the configuration directory so you'd have the proper links in<br>
> place.)<br>
><br>
> Therefore, I'd say that the approach you're using is the best one (at<br>
> least for now).<br>
><br>
</div></div>Why don't you run the two configurations under two different users? That would<br>
provide a straightforward way of separating the two sets of ~/.mythtv files.<br>
</blockquote><div><br>I considered this but the box is used for other things apart from myth. Thanks for the suggestion though!<br></div></div><br>