Ok this is driving me absolutely bonkers. I use a desktop as a DVR and compile myth from git. I don't use a service to run the backend just a simple entry in session and startup to run it once logged in. Naturally the system starts on it's own while I'm not around to record TV but myth doesn't always start, wtf? I can even run myth from cmd line when it fails to autostart with no issue. Can't find anything in the logs either, not that I know where to look either other than syslog and dmesg. If it makes any difference it's autostarted as root and the sudoers file has been edited to be able to exec sudo w/o a prompt. Please don't tell me how I shouldn't do that cause I already know the dangers. Or that I can't run myth as root, cause root has the same privileges as the user myth and the logged on user so it works just fine. Although I get the feeling this is where the issue is stemming from. If you must know I run as root so that it may use r/t threads where needed and higher priority threads where it sees fit. For some reason it wouldn't do so if run as normal user.
Adv Reply
Bookmarks