| Shred00 | is there any way to configure the mythtv-backend package to start just a mythjobqueue and not a whole mythbackend? | 11:01 |
|---|---|---|
| === dkeith_ is now known as dkeith | ||
| tgm4883 | Shred00, maybe, some things can be run outside of mythbackend, I think mythjobqueue might be one of them | 13:25 |
| Shred00 | tgm4883: mythjobqueue can definitely be run without mythbackend. the question is, given the structure of mythbunutu's /etc/init/mythtv-backend, how does one choose to not run the backend, other than hacking/removing that script (which ends up needing doing frequently on upgrades) | 13:26 |
| tgm4883 | Shred00, you shouldn't need to hack at the script between upgrades. If you've changed it, it shouldn't get overwritten | 13:27 |
| Shred00 | it does when it's changed upstream | 13:27 |
| Shred00 | or you at least get a "what do you want to do" prompt | 13:27 |
| tgm4883 | Shred00, it most certainly should not | 13:27 |
| tgm4883 | Shred00, yes, you will get the prompt | 13:28 |
| tgm4883 | but it's not overwritten automatically | 13:28 |
| tgm4883 | Shred00, what are the startup options for mythjobqueue? | 13:28 |
| tgm4883 | same as mythbackend? | 13:28 |
| Shred00 | tgm4883: no, of course not. i didn't mean to imply it was done without intervention. but still, i don't want to have to keep applying the same edits to that script every time it's upgraded and upstream updated it. i want to set it, once, and then forget it. | 13:28 |
| tgm4883 | Shred00, well just say you don't want to overwrite it then | 13:29 |
| Shred00 | tgm4883: they appear to be similar. i can't guarantee they are drop-in replacement though | 13:29 |
| tgm4883 | it looks like it just needs started | 13:30 |
| tgm4883 | http://www.mythtv.org/wiki/Mythjobqueue | 13:30 |
| Shred00 | right. the bigger detail is enabling a one-place setting for "backend: enable/disable", "jobqueue: enable/disable" | 13:31 |
| Shred00 | that doesn't get overwritten by upstream updates | 13:31 |
| tgm4883 | you can disable the backend by doing 'sudo touch /etc/init/mythtv-backend.override' | 13:32 |
| tgm4883 | we'll have to make a startup job for mythjobqueue | 13:32 |
| Shred00 | ahh. didn't know about .override | 13:33 |
| tgm4883 | Shred00, without testing it, something like this should work http://pastebin.ubuntu.com/5777103/ | 13:35 |
| tgm4883 | Shred00, actually, looks like someone did the work for us http://www.mythtv.org/wiki/Upstart_mythjobqueue_Configuration | 13:35 |
| Shred00 | yeah. just needs pulling into mythbuntu. but it shouldn't be run if the backend is running so it needs to be aware of that | 13:36 |
| tgm4883 | I'd rather have it do what the backend job does though and look for mysql started | 13:37 |
| tgm4883 | Shred00, well we'd probably want to split out the mythjobqueue package | 13:37 |
| Shred00 | sure, it can gate on mysql | 13:37 |
| tgm4883 | Shred00, also, it looks like you can do your job edits in the override file too instead of in the .conf file http://upstart.ubuntu.com/cookbook/#override-files | 13:39 |
| tgm4883 | Shred00, also, I was wrong, in order to disable startup, you need to put 'manual' in that override file, not just touch it | 13:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!