On Tue, 2008-04-29 at 16:20 +0000, laga wrote: > > If your "set top box" is set up to auto login (which can be done in > mythbuntu-control-centre), then irexec should already be running.
It's not. I forgo all of the "login" overhead. I don't see the point to starting up the whole login process (i.e. gdm and it's overhead) only to have it (automatically) log in the same user and start the same process every time. > Hacking it into /etc/init.d/lirc as you suggested earlier will most > likely make it hard to start X apps (because $DISPLAY won't be set). Right. I guess because my "set top box" environment is so predictable, I'm probably setting DISPLAY in the process that irexec calls to start/stop the myth frontend. > Also, irexec should be session-specific because every user might have > their own ~/.lircrc. Right. But in this "set top box" deployment there is no "every user". There is only one. > maybe LIRC should ship a xdg login script for irexec? But that again assumes the overhead of using gdm doesn't it? Or do you mean the stream of actions that an "xinit" would start? I don't recall where in the desktop standards "xdg" fits. b. ** Attachment added: "unnamed" http://launchpadlibrarian.net/14020452/unnamed -- startup script does not start irexec https://bugs.launchpad.net/bugs/224208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
