<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jan 18, 2008, at 1:09 PM, Enigma wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div bgcolor="#ffffff" text="#000000"> <blockquote type="cite"><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">Mysql 'owns' the </span></blockquote><blockquote type="cite"><font color="black" face="Verdana,Arial,Helvetica" size="2"><font color="black" face="Verdana,Arial,Helvetica" size="2"> scheduling process</font></font></blockquote> <br> I don't know what 'owns' is supposed to mean in this context, but the scheduling thread is spawned by mythbackend and runs under whatever user the backend is running. Similarly, mythfilldatabase runs as the same user as the backend if using automatic updates, or as the user who's crontab spawns it whwn run from cron. It is unclear to which of these instances you are referring since you refer to the "scheduling process" but then talk about mythfilldatabase failing (2 different activities), but either way, if he is running the backend as root the scheduler thread is running as root and any automatic updates will run as root. </div></blockquote><div><br class="webkit-block-placeholder"></div>I think he means that if mysql is not happy with something, scheduling will imply not function. He's making sure permissions that mysql needs are correct then the rest can do what it is supposed to do. So maybe mysql doesn't "own" the scheduling process, but it certainly can "p0wn3d" the scheduling process. :)</div><div><br class="webkit-block-placeholder"></div></body></html>