You should definitely try the script in $MATTERHORN_SOURCE/docs/felix/ bin/matterhorn_init_d.sh . This is intented to be copied to /etc/init.d/matterhorn, so that you can run it as a startup script, but it should work when run manually. It's syntax is similar to those scripts in /etc/init.d, obviously: matterhorn_init_d.sh start|stop|restart|status .
I have noticed some "deficiencies" in that script (at least, they are deficiencies for me), from an usability point of view. But this is my personal opinion as tester and developer, and maybe you will not feel these problems. Just give it a try and, if you think there's room for improvement, please feel free to comment here. Cheers, Rubén 2011/4/21 Hank Magnuski <[email protected]> > > Thank you, Josh, for the quick response. > > At this time it looks like MH 1.1 is up and running with a very clean start > on our test server. > > Thanks to all for your help, > > Hank > > > > On Thu, 21 Apr 2011, Josh Holtzman wrote: > > If you add this to the list of JVM arguments in start_matterhorn.sh (or >> add >> it to the JAVA_OPTS environment variable), the gogo shell won't expect >> standard input/out to be available. >> >> -Dgosh.args=--nointeractive >> >> Matterhorn stops immediately because the interactive shell can't get >> stdin. >> >> Josh >> > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
