<br><br><div class="gmail_quote">On 3 February 2012 22:34, Raymond Wagner <span dir="ltr"><<a href="mailto:raymond@wagnerrp.com">raymond@wagnerrp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
On 2/3/2012 17:19, David Crawford wrote:
</div><blockquote type="cite"><br>
<br>
<div class="gmail_quote"><div class="im">On 3 February 2012 22:17, Raymond Wagner
<span dir="ltr"><<a href="mailto:raymond@wagnerrp.com" target="_blank">raymond@wagnerrp.com</a>></span>
wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In the case
of the jobqueue, it currently passes everything through the<br>
Bourne shell (/bin/sh), but the end result would be the same.</blockquote>
</div></div>
<br><div class="im">
<div>Wouldnt that prevent the other script from not working also?
<br>
</div>
</div></blockquote>
<br>
The Bourne shell is merely told to run the command as given by a
string. It splits the string up into arguments based off quotation
and escaping, and then calls it using execv(). The arguments of
importance are the ones in whatever the last execv() call is, before
making it into the proper interpreter and your script. In the case
of the jobqueue, jobs are only routed through Bourne as a means of
"cheating", using the shell to split apart the arguments and manage
IO redirection rather than re-implementing such things internally.<br>
</div>
<br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">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>
<br></blockquote></div>Ok, any tips as how to configure bash so it might work? <div><br></div><div>last question for the day - i swear :)</div>