Jim,
On Debian, I can use /etc/rc.local to start programs as root (or as someone
else). For example, this starts some stuff to assist a MediaMVP I have that
runs mvpmc that's used to play back stuff in my wife's hobby room.
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
/usr/local/bin/mvprelay 16881 5906 6337 192.168.2.15 &
sudo -u freevo vlc -I telnet 2>/var/log/vlc &
exit 0
So theoretically, (and assuming it works on Fedora like it does on Debian) you
should be able to just put in
freevo recordserver start
freevo webserver start
freevo start
exit 0
I'm curious about your LTSP set-up. How many "freevo terminals" do you have,
and are they similar in hardware configuration, or different? How do you find
it as far as maintenance goes? How fast do the terminals boot up?
In my set-up, I have a central server running Debian which functions as a
Freevo web & record server, Samba file & print server, IMAP mail, Misterhouse
home automation, etc., which is the hub of my set-up. It presently tftp boots
the MediaMVP, and serves up the content to it and two other Freevo boxes which
have identical motherboards, but vary in remotes and other hardware. They
started life as Ubuntu 6 boxes, and have been "frankensteined" with upgrades
from both Ubuntu 7 and Freevo Debian packages and their dependencies. Needless
to say, they're getting to be a lot of work to maintain, and I've been thinking
about an LTSP or other net-booted disk image ideas.
To get there sometime in the future, I started by having a 'freevo' user on
each box, with the same UID/GID. My two Freevo "frontends" mount the freevo
home directory, which has a ~/.freevo directory, which contains just the cache
at the moment. So, the cache gets shared between the three machines
(main/record server which hosts /home, and the two "frontends"). Eventually, I
want to have one local_conf.py in the freevo home, and have it include the
appropriate /etc/freevo/local_conf.py which would contain the machine-specific
configuration items.
In the mean time, one AMD 3500 box boots off a SATA2 7200rpm disk (boots to
Freevo menu in about 45 seconds), and the other in the bedroom boots off a
sloooow Kingston 4GB flash drive in about 2 minutes. They're functional
enough, but it's getting to be a pain to maintain them.
Thanks for your time!
/Mike
----- Original Message ----
From: Jim Duda <j...@duda.tzo.com>
To: freevo-users@lists.sourceforge.net
Sent: Wednesday, January 28, 2009 10:30:21 AM
Subject: [Freevo-users] $HOME for /usr/bin/freevo start ?
I run freevo on different diskless computer machines in my house.
I use a modified version of the LTSP scripts for bootstrap from a tftp server.
I have to modify the scripts to keep LTSP4.2 compatible with newer versions of
fedora.
I've tried numerous ways to boot freevo automatically, all of which I get to
work somehow,
but most are usually hacks.
My distro is basically fedora 9 which boots from a central server.
The easiest method I've found is to run freevo as root (right or wrong)
and start freevo as a server from rc.d/init.d
<SNIP>
Thanks,
Jim
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
