23:17 < mattwire> Anyone interested in testing this patch? http://www.pastebin.ca/774031
23:17 < mattwire> It allows mythtv-setup to stop and start the backend automatically
23:18 < mattwire> and prevents the backend from being restarted until mythtv-setup finishes
23:23 -!- Netsplit heinlein.freenode.net <-> irc.freenode.net quits: jk1joel
23:23 -!- Netsplit over, joins: jk1joel
23:24 < gbee> might have a hard time selling this bit "sudo /etc/init.d/mythtv-backend stop"
23:24 < superm1> justinh, on your site you allude to a glasswide-osd, but i don't see up there, is that an oversight?
23:24 < laga> it's configurable, isn't it?
23:24 < gbee> laga: yeah, but that's the default
23:24 < justinh> superm1: it's built in
23:24 < superm1> justinh, ooh neat
23:24 < justinh> took a leaf out of mepo's book
23:25 < superm1> i was just wget'ing as we speak, so i haven't looked yet
23:25 < justinh> you can't wget it
23:25 < mattwire> there's two extra settings in the backend settings page to configure the stop and start command
23:25 < superm1> s/wget/download/
23:25 < mattwire> they also only run when on the master backend
23:29 < gbee> mattwire: I know, just suggesting you change the default
23:30 < mattwire> what would you suggest?
23:30 < mattwire> something like killall mythbackend?
23:30 < gbee> since users installing from source won't have an init script and using sudo is dubious, just mythbackend would be ok
23:30 < laga> distros can still patch it themselves
23:31 < gbee> mythbackend should be running under the same user as mythtv-setup, so permissions won't be an issue there and it
23:31 < gbee> laga: yep
23:31 < mattwire> ok
23:31 < mattwire> so "mythbackend" to start
23:31 < superm1> gbee, not necessarily will they run as the same user as mythtv-setup
23:31 < mattwire> and "killall mythbackend" to stop
23:31 < superm1> and what if extra options were passed to mythbackend?
23:32 < laga> superm1: we can patch that ourselves :)
23:32 < mattwire> superm1 - that's why it's configurable
23:32 < laga> maybe the patch could gather the switches from /proc/
23:32 < gbee> superm1: they should ... neither should be run as root
23:32 < mattwire> I use an init script so it does it all nicely for me
23:32 < Chutt> it really shouldn't automatically restart the backend.
23:33 < superm1> gbee, well in alot of our cases at least, mythtv-setup is ran as a user, but mythbackend has its own daemon userid
23:33 < mattwire> currently it only restarts the backend if it stopped it in the first place
23:33 < mattwire> and it asks you before stopping
23:33 < Chutt> mythbackend better be running as the same user as mythtv-setup, too
23:33 < Chutt> and the same user as the frontend
23:33 < gbee> aye
23:34 < laga> it's configurable so it doesn't really matter for distros
23:34 < superm1> why would the backend and frontend both need to be running as the same user though generally even though?
23:35 < laga> channel icons?
23:35 < Chutt> sharing ~/.mythtv/
23:35 < laga> although channel icons have the complete path AFAIK
23:35 < laga> so it's OK ;)
23:35 < superm1> Chutt, what in ~/.mythtv needs to be shared though? Especially if a systemwide mysql.txt is used
23:36 < Chutt> anything anyone wants to put in there
23:36 < mattwire> I'll submit a patch in trac for it at some point. It can use discussed as defaults. Any other major issues you
can see at the moment implementation wise?
23:36 < laga> superm1: lircrc
23:37 < mattwire> lirc isn't used on the backend because there's no gui
23:37 < superm1> you can use a remote in mythtv-setup? never thought to try :)
23:37 -!- DaveMorris [n=dave@host-212-158-244-26.bulldogdsl.com] has joined #mythtv
23:38 < laga> but lircrc doesn't really matter for mythbuntu since mythtv-setup and mythtv are run as the same user
23:38 < DaveMorris> !logs
23:41 -!- Cardoe [n=cardoe@gentoo/developer/Cardoe] has quit ["Leaving"]