On 6/20/05, Nick Rout <[EMAIL PROTECTED]> wrote:
> I wonder if this is more complex than it needs to be.
> 
> How about getting X to run on bootup straight into mythfrontend.
> 
> a startup script might contain (eg via /etc/init.d/local)
> 
> su - mythtv -c startx
> 
> and ~mythtv/.xinitrc contains:
> 
> exec mythfrontend

I *think* this will work but the problem I was worried about, and
granted xdm/gdm/whatever doesn't solve it, is that what happens when
the user makes a mistake and exits mythfrontend. (Or mythfrontend
crashes, etc.) Now I'm back at the command line somewhere (I think)
but the machine doesn't have a keyboard. (I've been looking at
autologin stuff) How does someone non computer literate get MythTV
running again? Power cycle?

Maybe there could be some sort of cron job that runs every so often
and figures out if the frontend was running and then restarts it (or
powers down safely) but I was hoping to not run cron on these frontend
boxes and thus almost never spin up the hard drives.

I also wondered about setting up some sort of monitor on the backend
machine that checks status on the frontend machines and takes some
sort of action if mythfrontend isn't running.

Just a bunch of not so well formed ideas.

> 
> Personally I am going to use the "power" button on my remote to trigger
> /sbin/halt for turning off.

I like that. There's also a shutdown config option within
mythtvfrontend that might help. I think that will require sudo which
always messes with my mind when I try to write rules taht don't
require password.

Thanks for the thoughts.

- Mark
> 
> 
> On Sat, 18 Jun 2005 16:05:51 -0700
> Mark Knecht wrote:
> 
> > I found 'entrance' but there are too many ~x86 packages for my liking.
> > Can anyone else recommend a graphical login manager that might have
> > the ability to allow a user to shut the system down from the login
> > screen? gdm wants to emerge pretty much all of gnome so I cannot use
> > that. xdm seems so sparce and doesn't allow shutdown.
> >
> > Thanks,
> > Mark
> >
> > --
> > [email protected] mailing list
> 
> --
> Nick Rout
> 
> --
> [email protected] mailing list
> 
>

-- 
[email protected] mailing list

Reply via email to